JIT status
Hi David, hi GCC team, What is the current status of JIT in GCC ? It does not currently work on macOS, with a bug in libgccjit.so linkage. We can work around it with a hack of the Make-lang.in (https://raw.githubusercontent.com/Homebrew/formula-patches/e9e0ee09389a54cc4c8fe1c24ebca3cd765ed0ba/gcc/6.1.0-jit.patch) but it seems to me that a proper solution would be use --version-script only conditional, with a check for symver support, and check whether -soname or -install_name should be passed to create the shared library. Homebrew (https://brew.sh) has been patching JIT support since GCC 6, and I’m considering simply dropping support for it when GCC 8 comes. Is there a chance I can this issue being fixed, or should I simply drop it? Cheers, FX
Re: JIT status
Hi FX, > What is the current status of JIT in GCC ? It does not currently work on > macOS, with a bug in libgccjit.so linkage. We can work around it with a > hack of the Make-lang.in > (https://raw.githubusercontent.com/Homebrew/formula-patches/e9e0ee09389a54cc4c8fe1c24ebca3cd765ed0ba/gcc/6.1.0-jit.patch) > but it seems to me that a proper solution would be use --version-script > only conditional, with a check for symver support, and check whether > -soname or -install_name should be passed to create the shared library. agreed ;-) I've had similar problems on Solaris, see PR jit/84288 for the details and an initial patch. Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University
Re: Google Summer of Code 2018: Call for mentors and ideas
Hi, I am happy to announce that we were selected as a Google Summer of Code 2018 mentor organization. At this point I am being asked to "invite mentors," so I will soon invite all the people who have expressed interest in the January email thread (or on IRC). If anybody has an additional idea for a GSoC project, please share it with us here and perhaps also add it to the Wiki page. If anybody else thinks of being a mentor this year, please write me an email, the sooner the better. I suspect that a google account is mandatory, though. Any other ideas/comments/suggestions are also welcome. Martin
Re: JIT status
On Tue, 2018-02-13 at 11:56 +0100, FX wrote: > Hi David, hi GCC team, > > What is the current status of JIT in GCC ? It does not currently work > on macOS, with a bug in libgccjit.so linkage. We can work around it > with a hack of the Make-lang.in (https://raw.githubusercontent.com/Ho > mebrew/formula- > patches/e9e0ee09389a54cc4c8fe1c24ebca3cd765ed0ba/gcc/6.1.0-jit.patch) > but it seems to me that a proper solution would be use --version- > script only conditional, with a check for symver support, and check > whether -soname or -install_name should be passed to create the > shared library. > > Homebrew (https://brew.sh) has been patching JIT support since GCC 6, > and I’m considering simply dropping support for it when GCC 8 comes. > Is there a chance I can this issue being fixed, or should I simply > drop it? I'd like to fix it, but I don't have access to a MacOS box. Is there a machine I can SSH into in the GCC compile farm, or similar public resource?
Re: JIT status
> I'd like to fix it, but I don't have access to a MacOS box. > > Is there a machine I can SSH into in the GCC compile farm, or similar > public resource? I’m happy to help, I can test stuff, etc. I can also provide (for limited amount of time) remote access to my own box, if you want. Let me know off-list what you need. FX