diff options
author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2021-08-08 21:57:02 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-08-08 21:57:02 +0000 |
commit | fa2aec10e60592348e1640b5bda0507b1324f235 (patch) | |
tree | 9d02fcb274469700637cdbde6e54e0fe81ff03e4 /gcc/omp-general.c | |
parent | 6bd42365fa2f46430fe933deaecd879857415fc4 (diff) | |
parent | 007e6ecefb0b43d0b9e7bf85f75ec050b5c520e5 (diff) | |
download | gcc-fa2aec10e60592348e1640b5bda0507b1324f235.zip gcc-fa2aec10e60592348e1640b5bda0507b1324f235.tar.gz gcc-fa2aec10e60592348e1640b5bda0507b1324f235.tar.bz2 |
Merge #615
615: lex: accept zero codepoints in strings r=philberty a=dkm
From Mark Wielaard : https://gcc.gnu.org/pipermail/gcc-rust/2021-August/000127.html
>
> Zero characters (codepoints) are acceptable in strings. The current
> Lexer::parse_string skipped such zero codepoints by accidents. The
> zero codepoint was also used as error/skip indicator, but that is only
> true if the third argument of utf8_escape_pair is true (yes, it is
> called pair, but is a triple).
>
> Add a testcase that checks the (sub)strings are separated by zero
> chars. Since we cannot slice strings yet this uses extern "C"
> functions, printf and memchr.
Co-authored-by: Mark Wielaard <mark@klomp.org>
Diffstat (limited to 'gcc/omp-general.c')
0 files changed, 0 insertions, 0 deletions