Re: glibc redefines SIGSTKSZ and MINSTKSZ (Re: pagure pushed to stress-ng (rawhide). "Fix build with glibc 2.34 (..more)")

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Tomasz Kłoczko:

> Is it not kind of a mistake in case of glibc to introduce such
> changes? (just asking to only have confirmation that it was not actual
> mistake and not to start another flame)

We don't have a choice.  The old interfaces are simply incompatible with
modern hardware.  CPUs have massive register files nowadays.
Applications using minimal signal stacks need to adapt in some way.

This is fallout from a hardware change.  I expect that related bugs will
be quite visible as Tiger Lake devices become more common.

Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux