On Tue, May 21, 2024 at 12:01 AM Max Filippov <jcmvb...@gmail.com> wrote: > On Mon, May 20, 2024 at 9:12 PM Waldemar Brodkorb <w...@openadk.org> wrote: > > Is the uClibc-ng port ready to commit or do you have any changes > > open? > > There's one fix for the xtensa port, I will resend the fixed version > in a couple days, > along with the new tags for the binutils and gcc. > > And then there's a conflict with the change made by the ARM port (reverted in > the second patch of the series) that involves gcc and for which I don't have > the > exact plan ATM. Let me take a good look at it.
So I tried to understand how to make a proper fix for this issue and I think that it must be done in the binutils. xtensa needs a binutils fix as well to be able to build working FDPIC static PIEs, but since nothing in the patch that adds xtensa FDPIC support to uclibc-ng depends on it, let's fix it separately. For now I've dropped the second patch from the xtensa FDPIC series for the uclibc-ng and the matching patch from the gcc with FDPIC support for xtensa. My current plan is to provide the fix for binutils that would handle init_array/fini_array pointers correctly in FDPIC static PIEs, then revert the workaround in the gcc (or restrict it only for ARM), then restrict the workaround in uclibc-ng to gcc versions that would still have the workaround. -- Thanks. -- Max _______________________________________________ devel mailing list -- devel@uclibc-ng.org To unsubscribe send an email to devel-le...@uclibc-ng.org
