--- Comment #24 from ian at airs dot com 2010-01-09 05:55 ---
This appears to be all fixed now.
--
ian at airs dot com changed:
What|Removed |Added
Status|UNC
--- Comment #23 from ubizjak at gmail dot com 2009-09-17 09:31 ---
Fixed?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36669
--- Comment #22 from hjl at gcc dot gnu dot org 2008-07-02 16:00 ---
Subject: Bug 36669
Author: hjl
Date: Wed Jul 2 15:59:19 2008
New Revision: 137369
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137369
Log:
gcc/
2008-07-02 H.J. Lu <[EMAIL PROTECTED]>
PR target/36
--- Comment #21 from hjl dot tools at gmail dot com 2008-07-02 03:52
---
(In reply to comment #19)
> This patch
>
> http://gcc.gnu.org/ml/gcc-patches/2008-07/msg00071.html
>
> makes all TF symbols with version GCC_4.3.0 while keeping the old
> version.
>
With this patch, on Linux/x8
--- Comment #20 from hjl dot tools at gmail dot com 2008-07-02 03:17
---
Created an attachment (id=15841)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15841&action=view)
A testcase
bash-3.2$ gcc --version
gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)
Copyright (C) 2008 Free Softwar
--- Comment #19 from hjl dot tools at gmail dot com 2008-07-02 03:15
---
This patch
http://gcc.gnu.org/ml/gcc-patches/2008-07/msg00071.html
makes all TF symbols with version GCC_4.3.0 while keeping the old
version.
--
hjl dot tools at gmail dot com changed:
What|Re
--- Comment #18 from rguenth at gcc dot gnu dot org 2008-07-01 08:56
---
We cannot "fix" this after the fact. And it's IMHO not worth it either.
We could add the symbol to GCC_4.3.0 as well and make that the default
though.
--
rguenth at gcc dot gnu dot org changed:
Wha
--- Comment #17 from hjl dot tools at gmail dot com 2008-07-01 04:07
---
(In reply to comment #16)
> So the question is whether we should break programs compiled by 4.3.0 and
> 4.3.1
> (acknowledging that there may not be any actual programs that break) in order
> to use consistent ver
--- Comment #16 from ian at airs dot com 2008-07-01 03:31 ---
So the question is whether we should break programs compiled by 4.3.0 and 4.3.1
(acknowledging that there may not be any actual programs that break) in order
to use consistent version numbers?
> 1. What version should x86-64
--- Comment #15 from hjl dot tools at gmail dot com 2008-06-30 19:50
---
(In reply to comment #13)
> The three symbols __gttf2, __lttf2, and __netf2 are part of the standard
> libgcc
> interface at version GCC_3.0. The fact that they are not supported by all
> instances of libgcc on a
--- Comment #14 from joseph at codesourcery dot com 2008-06-30 19:30
---
Subject: Re: Wrong versioning for __float128
On Mon, 30 Jun 2008, ian at airs dot com wrote:
> The three symbols __gttf2, __lttf2, and __netf2 are part of the standard
> libgcc
> interface at version GCC_3.0.
--- Comment #13 from ian at airs dot com 2008-06-30 19:12 ---
The three symbols __gttf2, __lttf2, and __netf2 are part of the standard libgcc
interface at version GCC_3.0. The fact that they are not supported by all
instances of libgcc on all platforms seems to me to be irrelevant. Whe
--- Comment #12 from hjl dot tools at gmail dot com 2008-06-30 18:30
---
Since config/i386/libgcc-x86_64-glibc.ver will be removed in
gcc 4.4 when __float128 is enabled for ia32, gcc 4.3 branch
will need a different patch if we want to fix it. Otherwise,
we can leave those symbols alone
--- Comment #11 from joseph at codesourcery dot com 2008-06-30 17:22
---
Subject: Re: Wrong versioning for __float128
On Mon, 30 Jun 2008, hjl dot tools at gmail dot com wrote:
> Joseph, my current patch:
>
> http://gcc.gnu.org/ml/gcc-patches/2008-06/msg01942.html
>
> changes it to
--- Comment #10 from hjl dot tools at gmail dot com 2008-06-30 17:08
---
Joseph, my current patch:
http://gcc.gnu.org/ml/gcc-patches/2008-06/msg01942.html
changes it to @@GCC_4.3.0 and adds
+%inherit GCC_4.4.0 GCC_4.3.0
+GCC_4.4.0 {
+}
to cc/libgcc-std.ver. I can also close it as WO
--- Comment #9 from joseph at codesourcery dot com 2008-06-30 13:39 ---
Subject: Re: Wrong versioning for __float128
On Mon, 30 Jun 2008, hjl dot tools at gmail dot com wrote:
> > > BTW, it turns out that gcc 4.3 has those __float128 functions in libgcc.a.
> > > That means all __float
--- Comment #8 from hjl dot tools at gmail dot com 2008-06-30 13:38 ---
(In reply to comment #7)
> Ok, so if we already shipped the "broken" version we cannot do anything here
> (WONTFIX), otherwise we can fix it.
>
That is my opinion.
BTW, I consider __float128 as experimental until
--- Comment #7 from rguenth at gcc dot gnu dot org 2008-06-30 13:35 ---
Ok, so if we already shipped the "broken" version we cannot do anything here
(WONTFIX), otherwise we can fix it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36669
--- Comment #6 from hjl dot tools at gmail dot com 2008-06-30 13:34 ---
(In reply to comment #3)
> Subject: Re: Wrong versioning for __float128
>
> On Mon, 30 Jun 2008, hjl dot tools at gmail dot com wrote:
>
> > BTW, it turns out that gcc 4.3 has those __float128 functions in libgcc.
--- Comment #5 from hjl dot tools at gmail dot com 2008-06-30 13:29 ---
(In reply to comment #4)
> HJ, why do you think they should be @@GCC_4.3.0? They got introduced with
>
> 2001-05-25 Richard Henderson <[EMAIL PROTECTED]>
>
>* libgcc-std.ver: Export XFmode and TFmode ver
--- Comment #4 from rguenth at gcc dot gnu dot org 2008-06-30 11:34 ---
HJ, why do you think they should be @@GCC_4.3.0? They got introduced with
2001-05-25 Richard Henderson <[EMAIL PROTECTED]>
* libgcc-std.ver: Export XFmode and TFmode versions of symbols.
--
rguenth at
--- Comment #3 from joseph at codesourcery dot com 2008-06-30 09:40 ---
Subject: Re: Wrong versioning for __float128
On Mon, 30 Jun 2008, hjl dot tools at gmail dot com wrote:
> BTW, it turns out that gcc 4.3 has those __float128 functions in libgcc.a.
> That means all __float128 func
--- 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 __float12
--- Comment #1 from ubizjak at gmail dot com 2008-06-30 06:01 ---
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.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36669
24 matches
Mail list logo
