On Fri, 28 Feb 2020, H.J. Lu wrote: > > > > However that hack has been actually made to address this very problem > > > > discussed with this submission, so why not simply sync our copy of > > > > libffi > > > > with the upstream version? Then we can decide if changing the hack into > > > > something cleaner is worth the hassle. > > > > > > I'd love to sync with upstream libffi. In fact, I have done it on my > > > users/hjl/cet/master > > > branch: > > > > > > https://gitlab.com/x86-gcc/gcc/-/commit/9090e840b8464ce0f684e305eb75ff4655d05deb > > I think we'd like to update as well, but isn't there an ABI change in libffi > > that has to be fixed first? > > Libffi 3.4 ABI was changed to support CET. But it isn't the first > time ABI change for libffi,
Have we made any conclusions WRT the way to move forward with this stuff? Things remain broken and I'd prefer to get the issues off the plate while the stuff is hot, or at least mildly warm. I'm about to get distracted with other work. Maciej
