From: Tom de Vries <Tom_deVries@mentor.com>
To: "gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: [committed] gen-pass-instances.awk: Rename var where to call_starts_at in handle_line
Date: Thu, 12 Nov 2015 10:05:00 -0000 [thread overview]
Message-ID: <56446429.80807@mentor.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
Hi,
this patch renames the rather generic variable 'where' to the more
specific 'call_starts_at' in handle_line in gen-pass-instances.awk.
Committed as to trunk as trivial.
Thanks,
- Tom
[-- Attachment #2: 0001-gen-pass-instances.awk-Rename-var-where-to-call_starts_at-in-handle_line.patch --]
[-- Type: text/x-patch, Size: 1080 bytes --]
gen-pass-instances.awk: Rename var where to call_starts_at in handle_line
2015-11-12 Tom de Vries <tom@codesourcery.com>
* gen-pass-instances.awk (handle_line): Rename var where to
call_starts_at.
---
gcc/gen-pass-instances.awk | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/gen-pass-instances.awk b/gcc/gen-pass-instances.awk
index b10c26a..311273e 100644
--- a/gcc/gen-pass-instances.awk
+++ b/gcc/gen-pass-instances.awk
@@ -43,8 +43,8 @@ function handle_line()
line = $0;
# Find call expression.
- where = match(line, /NEXT_PASS \((.+)\)/);
- if (where == 0)
+ call_starts_at = match(line, /NEXT_PASS \((.+)\)/);
+ if (call_starts_at == 0)
{
print line;
return;
@@ -59,7 +59,7 @@ function handle_line()
# Find pass_name argument
len_of_pass_name = len_of_call - (len_of_start + len_of_close);
- pass_starts_at = where + len_of_start;
+ pass_starts_at = call_starts_at + len_of_start;
pass_name = substr(line, pass_starts_at, len_of_pass_name);
# Find call expression prefix (until and including called function)
reply other threads:[~2015-11-12 10:05 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=56446429.80807@mentor.com \
--to=tom_devries@mentor.com \
--cc=gcc-patches@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).