aboutsummaryrefslogtreecommitdiff
path: root/gcc/gcov-io.h
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-08-08 21:57:02 +0000
committerGitHub <noreply@github.com>2021-08-08 21:57:02 +0000
commitfa2aec10e60592348e1640b5bda0507b1324f235 (patch)
tree9d02fcb274469700637cdbde6e54e0fe81ff03e4 /gcc/gcov-io.h
parent6bd42365fa2f46430fe933deaecd879857415fc4 (diff)
parent007e6ecefb0b43d0b9e7bf85f75ec050b5c520e5 (diff)
downloadgcc-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/gcov-io.h')
0 files changed, 0 insertions, 0 deletions