[fpc-devel] Summer of code collaboration
Florian Klämpfl
florian at freepascal.org
Sun Feb 10 20:48:49 CET 2013
Am 10.02.2013 20:12, schrieb Vittorio Giovara:
>
> Well the existence of external tools is what has allowed technology
> to foster and advance,
In a perfect world, with unlimited cpu resources, yes.
> eg have some common grounds and entry
> points... Your (limited) example is not exactly perfect, the tools
> that fpc bundle on windows are often outdated and conflict which the
> other tools
And you think this would change with llvm? The llvm is another tool
chain which might cause conflicts and being outdated. No matter if
windows or linux or whatever. Actually, linux might even be a bigger
pain because fpc would depend on the llvm offered by the distro.
> (off the top of my head mingw or ld).
This is exactly my point: cross compiling *to* windows is easy because
FPC does not depend on any external tool when building windows programs.
To any other platform is hard because of outdated *external* tools we
depend on. It does not matter what's the host system: the pain starts as
soon as external tools are involved.
>
> But I digress. The iOS experience could be improved in many ways, for
> example in Xcode you cannot set a breakpoint and when you do so with
> gdb all you get is an assembly viewer; having a LLVM backend could
> actually allow a better debugging
And you think llvm provides magically source code debugging info? When
just outputting llvm intermediate code, *all* source info is lost.
Actually, an llvm port requires another complete debugging info output
module to get debugging info.
More information about the fpc-devel
mailing list