This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/33532] bogus escape
- From: "wilson at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Sep 2007 22:53:17 -0000
- Subject: [Bug target/33532] bogus escape
- References: <bug-33532-2433@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from wilson at gcc dot gnu dot org 2007-09-24 22:53 -------
Echoing what Andrew Pinski already said, this isn't C code, this is RTL code,
the format of which is specified by the read-rtl.c file. Specifically, see the
read_brace_string function, which accepts backslash quoting exactly the same as
the read_quoted_string function. Unless you are proposing a change to the
read_brace_string function, there is nothing wrong with this code. Though I
will admit that the backslashes are unnecessary here and could optionally be
removed without harm.
If you are proposing changes to the read_brace_string function, it would have
been nice to mention that. If you want to find all such problems, changing
this function is probably the easiest way to do that. If you want to prevent
such problems from being reintroduced later, then you would definitely have to
change this function. Maybe add an argument to the read_escape function so
that we can handle calls from read_quoted_string differently than calls from
read_brace_string?
I have no idea at the moment why this matters to you. A little context might
be helpful.
--
wilson at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-09-24 22:53:17
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33532