On Tue, 15 Aug 2023, David Malcolm via Gcc-patches wrote:
> I'd prefer to reword this, as libgccjit was a poor choice of name for > the library (sorry!), to make it clearer it can be used for both ahead- > of-time and just-in-time compilation, and that as used for compilation, > the host considerations apply, not just those of the generated target > code. > > How about: > > The libgccjit library can, despite the name, be used both for > ahead-of-time compilation and for just-in-compilation. In both > cases it can be used to translate input representations (such as > source code) in the application context; in the latter case the > generated code is also run in the application context. > Limitations that apply to the compiler driver, apply here too in > terms of sanitizing inputs, so it is recommended that inputs are Unfortunately the lines that follow: > either sanitized by an external program to allow only trusted, > safe compilation and execution in the context of the application, again make a reference to a purely theoretical "external program" that is not going to exist in reality, and I made a fuss about that in another subthread (sorry Siddhesh). We shouldn't speak as if this solution is actually available to users. I know this is not the main point of your email, but we came up with a better wording for the compiler driver, and it would be good to align this text with that. Thanks. Alexander
