Simon Sobisch <simonsobi...@gnu.org> writes: > As GCC15 is now strict on dynamic function as > int *func() > to mean exactly zero arguments via its default -std=gnu23, I'm looking > into a dynamic option that would work for C23 and recognized libffi > being built as part of GCC and being part of its source tree, which > possibly is a way to go (unknown amount of arguments between 0 and > 252) > > But then I've seen that GCC's in-tree libffi was last updated in 2021, > while the current one is from this year. > > So I do wonder: > > 1 Which parts of GCC use libffi?
Think it's just Go right now and Rust may use it later. > 2 Is it linked in statically for GCC's usage (I'd see no problem via its > MIT license to put it anywhere)? Yes, it's statically linked. > 3 Is there a reason to _not_ update it in GCC16 to the most current > version? There were some regressions recently but I think master is fine now (and IIRC the last release is too, but would need to check). https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117635 tracks this. I was maybe going to look at it once zlib was done (just need to send it) but I'd be happy if someone else did it ;)
