On Wed, 20 Jul 2022 at 12:50, Ross Burton <[email protected]> wrote: > > On 20 Jul 2022, at 10:28, Alexander Kanavin via lists.openembedded.org > <[email protected]> wrote: > > > > On Wed, 20 Jul 2022 at 11:23, Richard Purdie > > <[email protected]> wrote: > >> That amounts to dropping x32 support because as soon as we remove these > >> tests, it will bitrot. > >> > >> There is still some value in the project being able to support > >> different architectures and different type sizes so I do still lean > >> towards keeping this alive at a minimal level. > > > > But then why not replace x32 with riscv32, which as well has 32 bit > > pointers but 64 bit integers and thus trips over the same type size > > issues? > > Does the RISC-V ecosystem care about riscv32? > > The problem with Intel x32 is that very few people care, so we end up fixing > upstream software. If RISC-V cares then we won’t be alone. > > Also, Intel should get to have an opinion on this. If they actually care > about x32 then they can help fix the issues, if they don’t then we can easily > switch to a platform that has support.
How much difference is there between x32 and riscv32 in upstreams? As they would trip on the same issues, one would assume that if the issue is fixed for one, it gets fixed for the other too. But might be that relevant upstreams need to have much of the code duplicated (fixing one copy does not fix the other) - ML
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#168354): https://lists.openembedded.org/g/openembedded-core/message/168354 Mute This Topic: https://lists.openembedded.org/mt/92500906/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
