This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/36669] Wrong versioning for __float128
- From: "hjl dot tools at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Jun 2008 06:14:40 -0000
- Subject: [Bug target/36669] Wrong versioning for __float128
- References: <bug-36669-682@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from hjl dot tools at gmail dot com 2008-06-30 06:14 -------
(In reply to comment #1)
> These are aliases to real functions, but I guess they should also be listed in
> gcc-4.3.0 section. Please send a patch to gcc-patches@ for discussion.
>
I doubt anyone is using __float128 seriously before the full __float128
run-time support is finished. Changing to @@GCC_4.3.0 will at most cause
run-time failure. Or we can leave it as is. Adding @@GCC_4.3.0 doesn't make
much senses if we will never remove the @@GCC_3.0 ones. If we do want to
remove the @@GCC_3.0 ones one day, now is a good time.
BTW, it turns out that gcc 4.3 has those __float128 functions in libgcc.a.
That means all __float128 functions are linked in as hidden functions.
Changing to @GCC_4.3.0 won't make any differences since the ones in
libgcc_s.so are never used.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36669