On Fri, Oct 20, 2023 at 04:12:48PM -0400, Jason Merrill wrote:
> On 8/24/23 09:58, Jakub Jelinek wrote:
> > The following patch implements C++26 unevaluated-string.
> > As it seems to me just extra pedanticity, it is implemented only for
> > -std=c++26 or -std=gnu++26 and later and only if -pedantic/-pedantic-errors.
>
> Hmm, I assumed it was accepted as a DR, but apparently not. In addition to
> making things ill-formed, it clarifies that these strings are never
> converted to the execution character set.
I believe we implement it that way. cp_parser_unevaluated_string_literal
(but several other spots as well) pass false to translate argument.
> Do we support cross-compilation
> to EBCDIC, which was the motivating context?
Do you mean EBCDIC just as execution charset, or translation charset as well?
There is some support for EBCDIC translation charset, but one needs iconv
with UTF-EBCDIC support, which glibc doesn't support, so I have no way to
actually verify it.
Jakub
