From: Mark Wielaard <mark@klomp.org>
To: Philip Herron <philip.herron@embecosm.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: [PATCH] lex: accept zero codepoints in strings
Date: Sun, 8 Aug 2021 15:05:35 +0200 [thread overview]
Message-ID: <YQ/Wn1Ltl/ZfxbYs@wildebeest.org> (raw)
In-Reply-To: <3ebee1a8-2c21-41e2-18e8-9b4248ef1551@embecosm.com>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Hi Philip
On Sun, Aug 08, 2021 at 01:36:21PM +0100, Philip Herron wrote:
> This patch looks good to go but the clang-format check is failing:
> https://github.com/Rust-GCC/gccrs/pull/615
>
> The error seems to be that it moves the extra check onto a new line.
> https://github.com/Rust-GCC/gccrs/pull/615/checks?check_run_id=3272823975
Unfortunately it doesn't show what the actual formatting isssue is. It
just say "Sign in for full log view". But I get the idea by running it
locally. The line is too long. Updated patch attached and pushed to
https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=str-zero
Cheers,
Mark
[-- Attachment #2: 0001-lex-accept-zero-codepoints-in-strings.patch --]
[-- Type: text/x-diff, Size: 2261 bytes --]
From 007e6ecefb0b43d0b9e7bf85f75ec050b5c520e5 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Sat, 7 Aug 2021 17:32:41 +0200
Subject: [PATCH] lex: accept zero codepoints in strings
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.
---
gcc/rust/lex/rust-lex.cc | 3 ++-
.../rust/execute/torture/str-zero.rs | 26 +++++++++++++++++++
2 files changed, 28 insertions(+), 1 deletion(-)
create mode 100644 gcc/testsuite/rust/execute/torture/str-zero.rs
diff --git a/gcc/rust/lex/rust-lex.cc b/gcc/rust/lex/rust-lex.cc
index 0b8a8eae651..49b6b6d32a7 100644
--- a/gcc/rust/lex/rust-lex.cc
+++ b/gcc/rust/lex/rust-lex.cc
@@ -1827,7 +1827,8 @@ Lexer::parse_string (Location loc)
else
length += std::get<1> (utf8_escape_pair);
- if (current_char32 != Codepoint (0))
+ if (current_char32 != Codepoint (0)
+ || !std::get<2> (utf8_escape_pair))
str += current_char32;
// required as parsing utf8 escape only changes current_char
diff --git a/gcc/testsuite/rust/execute/torture/str-zero.rs b/gcc/testsuite/rust/execute/torture/str-zero.rs
new file mode 100644
index 00000000000..e7fba0d1372
--- /dev/null
+++ b/gcc/testsuite/rust/execute/torture/str-zero.rs
@@ -0,0 +1,26 @@
+/* { dg-output "bar foo baz foobar\n" } */
+extern "C"
+{
+ fn printf(s: *const i8, ...);
+ fn memchr(s: *const i8, c: u8, n: usize) -> *const i8;
+}
+
+pub fn main () -> i32
+{
+ let f = "%s %s %s %s\n\0";
+ let s = "bar\0\
+ foo\
+ \x00\
+ baz\u{0000}\
+ foobar\0";
+ let cf = f as *const str as *const i8;
+ let cs = s as *const str as *const i8;
+ unsafe
+ {
+ let cs2 = memchr (cs, b'f', 5);
+ let cs3 = memchr (cs2, b'b', 5);
+ let cs4 = memchr (cs3, b'f', 5);
+ printf (cf, cs, cs2, cs3, cs4);
+ }
+ 0
+}
--
2.32.0
prev parent reply other threads:[~2021-08-08 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 15:45 Mark Wielaard
2021-08-08 12:36 ` Philip Herron
2021-08-08 13:05 ` Mark Wielaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YQ/Wn1Ltl/ZfxbYs@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=philip.herron@embecosm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).