https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87444
--- Comment #6 from George ---
Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87444
--- Comment #4 from George ---
Richard Biener,
Thanks for the reply. Unfortunately I don't understand what it means - whether
I should set explicitly the correct l2-cache-size or if that has any effect on
the final binary.
But I realise this ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87444
--- Comment #2 from George ---
Forgive me, I am not a developer and I am not aware how this was designed. But
may I ask: why was it designed to be wrong and why only on particular CPUs?
Also: what happens when a wrong l2-cache-size is used? Won'
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: studio at anchev dot net
Target Milestone: ---
STR:
gcc -### -march=native /usr/include/stdlib.h
lscpu | grep -i cache
OS: openSUSE Leap 15.0
EXPECTED:
gc