[fpc-devel] Blackfin support
DrDiettrich1 at aol.com
Tue Jul 13 01:46:16 CEST 2010
Florian Klaempfl schrieb:
> Hans-Peter Diettrich schrieb:
>> But since some abstract links already exist (class type
>> variables for machine specific descendants), these links could be
>> exchanged at runtime,
> One problem are all the used constants describing the target
> architecture. We discussed multiple back-ends in one compiler already in
> 2002 and saw no advantage in it so we didn't try to solve it and we
> decided to use the fpc -P ... solution which makes no difference for the
> For me, a much higher priority when doing rewrites might be
> multithreading nf the compiler itself.
That's questionable, depending on the real bottlenecks in compiler
operation. I suspect that disk I/O is the narrowest bottleneck, that can
not be widened by parallel processing. It also requires further
research, for e.g. the determination of the optimal number of threads,
depending on the currently available resources on a concrete machine.
But of course it's worth a try, to find out more...
More information about the fpc-devel