ChanServ changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
<sam_>
[02:31:34] <sam_> I'm sorry to intrude here, I'm just out of ideas -- the only person who can hit it is an apple silicon user using a gentoo vm
<sam_>
[02:31:48] <sam_> he seems to hit it on various packages with no common theme
chadmed_ has joined #asahi-alt
chadmed_ is now known as chadmed
<jannau>
works as expected with -march=armv8.4-a. at least from the as manpage it looks like it only accepts '-march=armv8.X-a' and not '-march=armv8-a+${EXTENSION}' like gcc seems to provide for -march=native
<jannau>
hmm, no. it just doesn't list the extensions
<jannau>
but the problem seems to be that gcc doesn't pass any of that along for -march=native: see `gcc -x assembler /dev/null -v -o /dev/null -c -march=native`
<jannau>
so -march=native looks broken
<jannau>
it passes '-march=native' along on x86_64
Glanzmann has joined #asahi-alt
chadmed has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi-alt
chadmed has quit [Read error: Connection reset by peer]
chadmed has joined #asahi-alt
mps has quit [Quit: leaving]
mps has joined #asahi-alt
<sam_>
interesting
<phire>
so not an asahi issue at all
<phire>
could this be related to the -pipe option? does that change how the assembler is lauched?
<sam_>
it uses shm instead of dumping the intermediate content into a file but i don't think it should affect options
<sam_>
but then again i wouldn't think this bug should happen in the first place