Georg-Johann Lay <a...@gjlay.de> writes:
>> 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.
No, on the contrary: the goal is to have all parts (target-dependent or
otherwise) of libgcc reside in libgcc and its subdirectories. This is
just like all other target libraries: you don't have target-dependent
libgfortran of libjava stuff in gcc/config.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
