[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2021-09-11 Thread luke-jr+gccbugs at utopios dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

--- Comment #16 from Luke Dashjr  ---
GCC only supports defaults now?

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2021-09-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

Andrew Pinski  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #15 from Andrew Pinski  ---
Right and mfunction-return=thunk was never the default in any GCC release,
there was no ABI change techincally.  It is only an ABI change because gentoo
decided to turn it the default for glibc.

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

--- Comment #14 from H.J. Lu  ---
(In reply to Luke Dashjr from comment #13)
> I run Gentoo, so it compiled it for me (2.27)

You should report it to Gentoo.

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

--- Comment #13 from Luke Dashjr  ---
I run Gentoo, so it compiled it for me (2.27)

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

--- Comment #12 from H.J. Lu  ---
(In reply to Luke Dashjr from comment #11)
> Simply upgrading to GCC 8.2.0 failed due to the multiple-definition of
> __x86_return_thunk, so I successfully built only the C compiler with the
> non-thunking defaults; from there, I rebuilt glibc again without thunking,
> then rebuilt the full GCC with thunking re-enabled, and glibc again with
> thunking re-enabled.
> 
> My most recent issue was with building distcc and libiberty.a, which I
> solved by removing binutils-libs and installing it again from scratch (a
> simple rebuild failed due to the multiple-definition of __x86_return_thunk
> in the existing library).

Where did you get your glibc?

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

--- Comment #11 from Luke Dashjr  ---
Simply upgrading to GCC 8.2.0 failed due to the multiple-definition of
__x86_return_thunk, so I successfully built only the C compiler with the
non-thunking defaults; from there, I rebuilt glibc again without thunking, then
rebuilt the full GCC with thunking re-enabled, and glibc again with thunking
re-enabled.

My most recent issue was with building distcc and libiberty.a, which I solved
by removing binutils-libs and installing it again from scratch (a simple
rebuild failed due to the multiple-definition of __x86_return_thunk in the
existing library).

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

--- Comment #10 from H.J. Lu  ---
(In reply to Luke Dashjr from comment #9)
> Is there a solution or workaround for this? I already rebuilt glibc more
> than once, but keep running into it... (GCC 8.2.0 on a system that was
> mostly built by 7.3.0)

What exactly have you done?

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2019-03-16 Thread luke-jr+gccbugs at utopios dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

Luke Dashjr  changed:

   What|Removed |Added

 CC||luke-jr+gccbugs at utopios dot 
org

--- Comment #9 from Luke Dashjr  ---
Is there a solution or workaround for this? I already rebuilt glibc more than
once, but keep running into it... (GCC 8.2.0 on a system that was mostly built
by 7.3.0)

[Bug target/85915] ABI incompatibility (multiple definition of `__x86_return_thunk') for static libraries, between GCC 7.3.0 and GCC >=7.4.0, caused by -mfunction-return=thunk

2018-05-27 Thread Arfrever.FTA at GMail dot Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85915

Arfrever Frehtes Taifersar Arahesis  changed:

   What|Removed |Added

Summary|ABI incompatibility |ABI incompatibility
   |(multiple definition of |(multiple definition of
   |`__x86_return_thunk')   |`__x86_return_thunk') for
   |between GCC 7.3.0 and GCC   |static libraries, between
   |>=7.4.0 caused by   |GCC 7.3.0 and GCC >=7.4.0,
   |-mfunction-return=thunk |caused by
   ||-mfunction-return=thunk

--- Comment #8 from Arfrever Frehtes Taifersar Arahesis  ---
It seems that this ABI incompatibility affects all static libraries, not just
libc_nonshared.a.