On Wed, May 11, 2022 at 10:01 PM David Malcolm via Gcc-patches <gcc-patches@gcc.gnu.org> wrote: > > On Wed, 2022-05-11 at 15:04 -0400, Eric Gallager wrote: > > On Wed, May 11, 2022 at 9:53 AM David Malcolm via Gcc-patches > > <gcc-patches@gcc.gnu.org> wrote: > > > > > > On Thu, 2022-05-05 at 14:16 +0200, Martin Liška wrote: > > > > Patch can bootstrap on x86_64-linux-gnu and survives regression > > > > tests. > > > > > > > > Ready to be installed? > > > > > > I looked over the changes to: > > > > > > gcc/analyzer/*.cc > > > gcc/input.cc > > > gcc/jit/*.cc > > > > > > and they look good to me. > > > > > > I assume that you enabled "jit" during the testing, right? (it's > > > not > > > in --enable-languages=all, which is a perennial source of issues). > > > > > > > So, what remains to be done to include "jit" in "all" anyways? Are > > there still some platforms left that it's not supported on yet or > > something? > > IIRC the issue was that it requires --enable-host-shared, which slows > down the compiler for everyone else by a few percent (since it requires > the compiler to be built as position-independent code).
And with all symbols exported aka interposable. Maybe we could funnel in -fno-semantic-interposition ... (and see if it makes a difference) Richard. > > Dave >
