Ian Lance Taylor schrieb:
> Georg-Johann Lay <a...@gjlay.de> writes:
> 
>> Ian Lance Taylor schrieb:
>>> Georg-Johann Lay <a...@gjlay.de> writes:
>>>
>> Wondering why there is now just another t-target, both t-targets
>> containing snips of libgcc.
> 
> There is a very slowly moving incomplete transition to move all the
> libgcc configury support and sources from gcc/config/* to
> libgcc/config/*.
> 
> If you are creating new files you can help that transition by creating
> them in libgcc rather than gcc.

May I say that I like the "classical" setup more because all target
dependent code resides in
   ./gcc/config/$target
(besides some lines for adding a target and some hacks in
./gcc/longlong.h that could easily be moved into target directory)

I don't like that scattering of target dependent parts. Target
dependent libgcc parts could just the same way reside in
   ./gcc/config/$target/libgcc/
instead of
   ./libgcc/config/$target/
and maybe many other places.

Johann




Reply via email to