From: Tom de Vries <Tom_deVries@mentor.com>
To: Richard Biener <rguenther@suse.de>,
Alan Lawrence <alan.lawrence@arm.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Michael Matz <matz@suse.de>
Subject: Re: [PING^2] [PATCH][5a/5] Postpone expanding va_arg until pass_stdarg
Date: Tue, 09 Jun 2015 13:03:00 -0000 [thread overview]
Message-ID: <5576E293.9030006@mentor.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1506091301120.30088@zhemvz.fhfr.qr>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On 09/06/15 13:03, Richard Biener wrote:
> On Tue, 9 Jun 2015, Alan Lawrence wrote:
>
>> Hmmm. One side effect of this is that the line number information available in
>> the target hook gimplify_va_arg_expr, is now just the name of the containing
>> function, rather than the specific use of va_arg. Is there some way to get
>> this more precise location (e.g. gimple_location(stmt) in expand_ifn_va_arg_1,
>> the only caller of said hook)? I don't really want to have to add an extra
>> parameter to the target hook...
>
> The x86 variant doesn't use any locations but if then the caller of
> the target hook (expand_ifn_va_arg_1) should assign the IFNs location
> to all statements expanded from it (it could set input_location to
> that during the target hook call...)
>
That seems to work.
The scan-assembler-not test in the testcase in attached patch:
- fails without the expand_ifn_va_arg_1 patch hunk, and
- passes with that hunk.
I'll put it through bootstrap and reg-test on x86_64.
OK for trunk if that goes well?
Thanks,
- Tom
[-- Attachment #2: 0001-Handle-location-in-expand_ifn_va_arg_1.patch --]
[-- Type: text/x-patch, Size: 2113 bytes --]
Handle location in expand_ifn_va_arg_1
2015-06-09 Tom de Vries <tom@codesourcery.com>
* tree-stdarg.c (expand_ifn_va_arg_1): Handle location.
* gcc.target/i386/vararg-loc.c: New test.
---
gcc/testsuite/gcc.target/i386/vararg-loc.c | 27 +++++++++++++++++++++++++++
gcc/tree-stdarg.c | 4 ++++
2 files changed, 31 insertions(+)
create mode 100644 gcc/testsuite/gcc.target/i386/vararg-loc.c
diff --git a/gcc/testsuite/gcc.target/i386/vararg-loc.c b/gcc/testsuite/gcc.target/i386/vararg-loc.c
new file mode 100644
index 0000000..f236fe3
--- /dev/null
+++ b/gcc/testsuite/gcc.target/i386/vararg-loc.c
@@ -0,0 +1,27 @@
+/* { dg-do compile } */
+/* { dg-options "-g -O0" } */
+
+#include <stdarg.h>
+
+int /* 6. */
+ /* 7. */
+f (int a, ...) /* 8. */
+ /* 9. */
+{
+
+ int sum = a;
+
+ va_list ap;
+
+ va_start (ap, a);
+
+ sum += va_arg (ap, int); /* 18. */
+
+ sum += va_arg (ap, int); /* 20. */
+
+ return sum;
+}
+
+/* { dg-final { scan-assembler-not "\\.loc 1 \[6789\] 0" } } */
+/* { dg-final { scan-assembler-times "\\.loc 1 18 0" 1 } } */
+/* { dg-final { scan-assembler-times "\\.loc 1 20 0" 1 } } */
diff --git a/gcc/tree-stdarg.c b/gcc/tree-stdarg.c
index 08d10b5..65fe9f9 100644
--- a/gcc/tree-stdarg.c
+++ b/gcc/tree-stdarg.c
@@ -1031,6 +1031,7 @@ expand_ifn_va_arg_1 (function *fun)
bool modified = false;
basic_block bb;
gimple_stmt_iterator i;
+ location_t saved_location;
FOR_EACH_BB_FN (bb, fun)
for (i = gsi_start_bb (bb); !gsi_end_p (i); gsi_next (&i))
@@ -1051,6 +1052,8 @@ expand_ifn_va_arg_1 (function *fun)
ap = build_fold_indirect_ref (ap);
push_gimplify_context (false);
+ saved_location = input_location;
+ input_location = gimple_location (stmt);
/* Make it easier for the backends by protecting the valist argument
from multiple evaluations. */
@@ -1081,6 +1084,7 @@ expand_ifn_va_arg_1 (function *fun)
else
gimplify_expr (&expr, &pre, &post, is_gimple_lvalue, fb_lvalue);
+ input_location = saved_location;
pop_gimplify_context (NULL);
gimple_seq_add_seq (&pre, post);
--
1.9.1
next prev parent reply other threads:[~2015-06-09 12:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 10:48 [stage1] " Tom de Vries
2015-02-19 10:51 ` [PATCH][1/5] Disable lang_hooks.gimplify_expr in free_lang_data Tom de Vries
2015-02-19 12:41 ` Richard Biener
2015-02-19 10:59 ` [PATCH][2/5] Add gimple_find_sub_bbs Tom de Vries
2015-02-19 12:41 ` Richard Biener
2015-02-19 12:51 ` Jakub Jelinek
2015-02-19 13:03 ` Marek Polacek
2015-02-19 13:31 ` Richard Biener
2015-02-19 13:07 ` Richard Biener
2015-02-22 12:47 ` Tom de Vries
2015-02-19 11:06 ` [PATCH][3/5] Factor optimize_va_list_gpr_fpr_size out of pass_stdarg::execute Tom de Vries
2015-02-19 12:44 ` Richard Biener
2015-02-19 11:37 ` [PATCH][4/5] Handle internal_fn in operand_equal_p Tom de Vries
2015-02-19 12:49 ` Richard Biener
2015-02-19 12:59 ` Jakub Jelinek
2015-02-19 13:09 ` Richard Biener
2015-02-19 15:31 ` Tom de Vries
2015-02-20 11:59 ` Richard Biener
2015-02-22 13:13 ` Tom de Vries
2015-02-23 10:19 ` Richard Biener
2015-02-24 13:09 ` Fwd: " Tom de Vries
2015-02-19 12:08 ` [PATCH][5/5] Postpone expanding va_arg until pass_stdarg Tom de Vries
2015-02-19 13:05 ` Richard Biener
2015-02-22 13:24 ` Tom de Vries
2015-02-23 9:03 ` Michael Matz
2015-02-23 10:36 ` Tom de Vries
2015-02-24 8:26 ` Tom de Vries
2015-03-10 15:31 ` [PING] [PATCH][5b/5] Avoid running expand_ifn_va_arg_1 in functions without va_arg Tom de Vries
2015-04-16 8:50 ` [PING^2] " Tom de Vries
2015-04-16 8:56 ` Richard Biener
2015-03-10 15:31 ` [PING] [PATCH][5a/5] Postpone expanding va_arg until pass_stdarg Tom de Vries
2015-04-16 8:50 ` [PING^2] " Tom de Vries
2015-04-16 8:55 ` Richard Biener
2015-04-21 5:32 ` Bin.Cheng
2015-06-09 11:04 ` Alan Lawrence
2015-06-09 11:07 ` Richard Biener
2015-06-09 13:03 ` Tom de Vries [this message]
2015-06-09 13:07 ` Richard Biener
2015-06-09 13:30 ` Alan Lawrence
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=5576E293.9030006@mentor.com \
--to=tom_devries@mentor.com \
--cc=alan.lawrence@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=matz@suse.de \
--cc=rguenther@suse.de \
/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).