Etienne and I also discussed moving libffi out of the gcc tree and
into its own repository somewhere. I'd prefer not to do this. My
impression was that Etienne could find someone to do releases and that
sort of thing, but that doing actual libffi maintenance was too much
work. One nice advantage of keeping the code in the gcc tree is that
there are many platform and ABI experts around, so we can run the
various bits of assembly code past them for approval. I think getting
this sort of review out-of-tree would be much more difficult.
Anything else?