bug#43725: 28.0.50; Include feature/native-comp into master

[Andrea Corallo]

Eli Zaretskii <eliz@gnu.org> writes:

> One issue that I have in my notes about native-comp is the issue with
> input encoding of the source we submit to the native-compiler.
>
> The issue is this: our Lisp files are generally encoded in UTF-8.  But
> there's no guarantee that GCC expects the source to be encoded in
> UTF-8.  If the text we submit to libgccjit for compilation is in the
> same encoding as the original .el files, then shouldn't we tell GCC
> its actual encoding, to make sure non-ASCII text aren't mangled?

The only generated text we are passing to libgccjit is feed to
'gcc_jit_context_new_string_literal'.  This text is generated from
'Fprin1_to_string' that we use to essentially render in form of text
immediate objects.  I thought this was disconnected from the encoding of
the source file, am I wrong?

Thanks

  Andrea