Closed powpingdone closed 2 weeks ago
There is no 32bits support in Oryon1 CPU Cores.
That's kinda what I figured, but I didn't find a solid source anywhere.
That's a trending with new chips anyway. Cortex X, M1, Oryon... All have droped the 32bits support to save some silicon.
Side note, the official naming is "X", with 2 derivative: X-Elite and X-Plus.
If you're talking about the X1E
naming stuff, I'll go ahead and modify it to be something more readable.
I'm sorry that I have to ask this, but what's the best way to test these flags for compatibility?
I'm sorry that I have to ask this, but what's the best way to test these flags for compatibility?
What do you mean? Testing if the binary build and run on an X-Elite/X-Plus laptop running linux?
Yeah, kinda. Making sure I don't run into instructions that aren't in the CPU. I might have blown away my previous Gentoo install with these compiler flags, even though I copied them from the GCC repo. I already have (abused) a X1E laptop into Linux, so it's not a issue of not having the device.
It does pass the test suite with -fsanitize={undefined,address}
and no sanitizer on gcc-13, so it might be ok.
I'm going to presume if it passes the tests, then it's "ok."
looks good to me. I'll try to test later (tomorrow?)
Some compiler flags for the Oryon1 support. I still need to test this. I don't believe that this cpu has 32 bit support, though I'm not 100% sure.