Alexander Kabaev <[EMAIL PROTECTED]> writes:
> I also noticed that on Linux glibc implements some of the libgcc
> symbols, namely _Unwind_Find_FDE and __register_frame_info_bases family
> of functions. I wonder why it is done and if I missed something obvious
> here.
It seems to have to do with some old compatibility issues. There are
some e-mail threads here:
http://sourceware.org/ml/libc-alpha/2001-09/msg00187.html
http://sourceware.org/ml/libc-alpha/2001-10/msg00002.html
> I wonder if GCC team will be willing to accept gcc part of my changes
> into mainstream sources if I submit a patch. What are chances of
> something like this to be committed into not only trunk, but also GCC
> 4.1, 4.2 and 4.3 branches? FreeBSD 7.0 wants to ship with GCC 4.1, but
> newer version is likely to be imported into trunk shortly after CVS is
> branched for 7.0 release.
Yes. In general gcc will accept target specific changes that do not
affect any other targets for release branches.
(You do have to have a copyright assignment--I didn't check whether
you already have one.)
Ian
