https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
Jonathan Wakely changed:
What|Removed |Added
Keywords||ABI
--- Comment #8 from Jonathan Wakel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
James Y Knight changed:
What|Removed |Added
CC||foom at fuhm dot net
--- Comment #7 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
--- Comment #5 from Jonathan Wakely ---
(In reply to Duarte from comment #2)
> One option could be to just use whatever values linux uses :)
The linux kernel allows the cache line sizes to be set at boot (for some h/w)
which doesn't really map w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
--- Comment #4 from Duarte ---
Oh, I see; thanks for pointing that out.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
--- Comment #3 from Jonathan Wakely ---
(In reply to Duarte from comment #0)
> It seems, however, that neither std::hardware_destructive_interference_size
> nor std::hardware_constructive_interference_size have been included in
> libstdc++.
As c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
--- Comment #2 from Duarte ---
I don't think it should be the min size. For example, architectures with 64bit
cache lines can have prefetchers that immediately fetch adjacent cache lines,
in which case the value should be 128.
One option could b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466
--- Comment #1 from Andrew Pinski ---
Hmm, these are interesting defined on some architures. On AARCH64, there are
at least two different values that can be defined here (I suspect it should be
the min of the two), 128 and 64 but architurially t
