From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH] c: Delete a stray line in asm inline
Date: Sat, 08 Dec 2018 22:27:00 -0000 [thread overview]
Message-ID: <2c3d1624f7f876cbb62c14fb26432ce65ab5e4ce.1544297869.git.segher@kernel.crashing.org> (raw)
I noticed I accidentally copied a line too many from the "volatile"
handling to the "inline" handling. This fixes it.
Tested on powerpc64-linux {-m32,-m64}; committing as trivial and obvious.
Segher
2018-12-08 Segher Boessenkool <segher@kernel.crashing.org>
gcc/c/
* c-parser (c_parser_asm_statement) [RID_INLINE]: Delete stray line
setting "quals".
---
gcc/c/c-parser.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/gcc/c/c-parser.c b/gcc/c/c-parser.c
index 3a7fcdc..b875c4f 100644
--- a/gcc/c/c-parser.c
+++ b/gcc/c/c-parser.c
@@ -6389,7 +6389,6 @@ c_parser_asm_statement (c_parser *parser)
if (!is_inline)
{
is_inline = true;
- quals = c_parser_peek_token (parser)->value;
c_parser_consume_token (parser);
}
else
--
1.8.3.1
reply other threads:[~2018-12-08 22:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2c3d1624f7f876cbb62c14fb26432ce65ab5e4ce.1544297869.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
/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).