Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36565 - glibc: use lock elision per default
Attached to Project:
Arch Linux
Opened by Michael Werner (Xaseron) - Friday, 16 August 2013, 15:09 GMT
Last edited by Allan McRae (Allan) - Sunday, 25 August 2013, 03:55 GMT
Opened by Michael Werner (Xaseron) - Friday, 16 August 2013, 15:09 GMT
Last edited by Allan McRae (Allan) - Sunday, 25 August 2013, 03:55 GMT
|
DetailsWhy don't we enable lock elision per default in the glibc? It can enhance the multithread performance on Intel Haswell prozessors and would not harm any other cpu architecture.
more information: http://lwn.net/Articles/533894/ configure parameter: --enable-lock-elision=yes |
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 25 August 2013, 03:55 GMT
Reason for closing: Implemented
Additional comments about closing: glibc-2.18-3 in [testing]
Sunday, 25 August 2013, 03:55 GMT
Reason for closing: Implemented
Additional comments about closing: glibc-2.18-3 in [testing]
Comment by Allan McRae (Allan) -
Friday, 16 August 2013, 21:57 GMT
Short answer is I do not think it is ready yet.
Comment by Allan McRae (Allan) -
Monday, 19 August 2013, 10:10 GMT
I will build glibc with this later in the week (provided no more issues with the new release arrive that I need to patch), and stick it in [testing] for a while.