Re: x86-64 -mtls-dialect=gnu2 change needs to be postponed

2024-02-12 Thread Florian Weimer
* Stephen Smoogen:

> On Sun, 11 Feb 2024 at 09:35, Florian Weimer  wrote:
>
>  We've hit an ABI ambiguity/bug:
>
>gcc: -mtls-dialect=gnu2 produces wrong code on x86-64
>
>
> Was this set for the Fedora 40 mass rebuild or something that was put
> in later? If it was put into the mass rebuild, what problems would it
> cause currently?

I couldn't get the testing done in time for the mass rebuild, so it
wasn't included.  It's fully interoperable, so an incremental transition
is okay (once we settled the ABI issue).

Thanks,
Florian
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: x86-64 -mtls-dialect=gnu2 change needs to be postponed

2024-02-12 Thread Stephen Smoogen
On Sun, 11 Feb 2024 at 09:35, Florian Weimer  wrote:

> We've hit an ABI ambiguity/bug:
>
>   gcc: -mtls-dialect=gnu2 produces wrong code on x86-64
>   
>
>
Was this set for the Fedora 40 mass rebuild or something that was put in
later? If it was put into the mass rebuild, what problems would it cause
currently?



> Apart from that, support in the GNU toolchain seems to be quite good.
> In particular, GDB handled the situation in the polymake crash quite
> well (reporting TLS data as uninitialized for the thread before the
> critical call, and producing the correct address for the variable
> afterwards).
>
> Thanks,
> Florian
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


x86-64 -mtls-dialect=gnu2 change needs to be postponed

2024-02-11 Thread Florian Weimer
We've hit an ABI ambiguity/bug:

  gcc: -mtls-dialect=gnu2 produces wrong code on x86-64
  

Apart from that, support in the GNU toolchain seems to be quite good.
In particular, GDB handled the situation in the polymake crash quite
well (reporting TLS data as uninitialized for the thread before the
critical call, and producing the correct address for the variable
afterwards).

Thanks,
Florian
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue