FreeBSD 3.x

Marc Espie espie@quatramaran.ens.fr
Sat Jun 5 17:26:00 GMT 1999


In article < Pine.LNX.4.05-df.9906042327150.29752-100000@bartlet.df.lth.se > you write:
>One other problem with *BSD and rbug.c is that the ___fixunsdfdi
>function in libc is buggy. NetBSD has fixed that in the latest release,
>but I don't know about the other *BSD.

I've finally checked that bug problem (after some hunting, it's 
NetBSD 6314), and our libc function is buggy as well...

However, it took me quite a while to reproduce that specific bug.
What does the netbsd compiler do that is different ?
our specific flavor of egcs, under normal circumstances, does call the
linker with -lgcc -lc -lgcc, so it picks up the version in libgcc.

Unless you manage not to get fixunsdfdi from libgcc, by either fiddling
with the compiler building not to build a full libgcc, or by fiddling with
the specs to link with libc first, you should always get the correct version.

As far as OpenBSD  goes, I don't know what to do with that bug-report yet.
Not only is this fairly obscure, but with our current setup, the libc 
flavor of these function is hardly ever called (only for other libc functions
as far as I've found), so what use are they ?

Sorry if this looks a bit like internal affairs from the BSDs, but I figure
that since it involves libgcc quite a bit, it's still relevant to the problem
at hand.


More information about the Gcc mailing list