This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nptl/17351] No hardware with functional lock elision available


https://sourceware.org/bugzilla/show_bug.cgi?id=17351

--- Comment #7 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Cedric BAIL from comment #6)
> Oh, I see ! Well, I guess I should consider protecting the user of my
> library by inserting the same hack that will turn of elision. It will reduce
> the potential instability they face and wont hurt at all as their is no
> hardware where this work.
> 
> Thanks for your help explaining glibc position.

There is no official glibc position.

I speak only for the Fedora glibc position.

While I am also an FSF Steward for glibc I don't suppose to know what position
the community will take on this topic. The community is consensus driven, so if
you want to know which direction the community is going to go ask on
libc-alpha.

If asked I would encourage the community to take the same position that Fedora
and Arch Linux (according to your comments) have taken.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]