This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFA: Fix other/44566
Steven Bosscher wrote:
> The only reason would be, AFAIU, that you can't compile one source
> file to code for two targets. This seems to be the direction hardware
> is taking, with many co-processors for dedicated tasks.
That's a good point, and I certainly agree that this is indeed a popular
hardware architecture direction. I also agree that you cannot in all
cases separate the code into multiple files, not just for reasons of
code structure, but because you may need the compiler to see both sets
of code at once. But, the hardware achitecture trend seems a strong
argument for doing the (large) project that Joseph estimated previously,
to build a robust multi-target compiler, not an argument for doing
something rather more fragile.
All the work people are doing to help turn things into hooks, and such,
is of course a step in the right direction; part of what we need for
this is to avoid having target macros affecting the front- and
middle-end compiler components.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713