#resolve-march-native on Arrow Lake

1 messages · Page 1 of 1 (latest)

robust gulch
#

hi, when attempting to compile gcc i run into an issue where it complains that -march=native cannot be resolved because my processor is a hybrid architecture, and it recommends the use of resolve-march-native (with a warning that it'll have different output depending on the core that runs it

this is indeed the case, and the line size of the l1 cache along with the regular size alternate between two different values (presumably for the P and E cores)
which value should i go with? one core type has a line size of 48 and the other has a line size of 32, would the bigger one be more optimal or dangerous or

prisma cedar
robust gulch
#

"Using either choice should eliminate the error with gcc. Yes, ideally you would pick which one corresponds to your usage pattern. If in doubt, take a guess. Both should work, and if you pick wrong, the only consequence should be that you encourage gcc to generate code that runs slightly less well due to it planning for the wrong L1 cache size. I would not expect the generated code to produce the wrong results, only to be larger/smaller than optimal, and somewhat slower. Outside of very CPU-intensive applications, I doubt you will notice the difference"

#

bawh

robust gulch
#

are there any proper recommendations?