From: Tom de Vries <Tom_deVries@mentor.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
Andrew MacLeod <amacleod@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [testsuite, committed] Use relative line number in gcc.dg/Walloca-14.c
Date: Wed, 02 Aug 2017 13:29:00 -0000 [thread overview]
Message-ID: <aa8a659f-b201-5c42-1fe0-01947b21839a@mentor.com> (raw)
In-Reply-To: <0c48f7c0-6fff-c8f3-5680-e4a0fc3203bf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
[ was: Re: Avoid generating useless range info ]
On 06/28/2017 09:56 AM, Aldy Hernandez wrote:
> void *q = __builtin_alloca (p); /* { dg-warning "passing argument 1" } */
> + /* { dg-warning "unbounded use of 'alloca'" "unbounded" { target *-*-* } 11 } */
Hi,
Please use relative line number next time.
Committed.
Thanks,
- Tom
[-- Attachment #2: 0001-Use-relative-line-number-in-gcc.dg-Walloca-14.c.patch --]
[-- Type: text/x-patch, Size: 752 bytes --]
Use relative line number in gcc.dg/Walloca-14.c
2017-08-02 Tom de Vries <tom@codesourcery.com>
* gcc.dg/Walloca-14.c: Use relative line number.
---
gcc/testsuite/gcc.dg/Walloca-14.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/gcc.dg/Walloca-14.c b/gcc/testsuite/gcc.dg/Walloca-14.c
index f3e3f57..ea48227 100644
--- a/gcc/testsuite/gcc.dg/Walloca-14.c
+++ b/gcc/testsuite/gcc.dg/Walloca-14.c
@@ -9,6 +9,6 @@ g (int *p)
extern void f (void *);
void *q = __builtin_alloca (p); /* { dg-warning "passing argument 1" } */
- /* { dg-warning "unbounded use of 'alloca'" "unbounded" { target *-*-* } 11 } */
+ /* { dg-warning "unbounded use of 'alloca'" "unbounded" { target *-*-* } .-1 } */
f (q);
}
prev parent reply other threads:[~2017-08-02 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 16:41 Avoid generating useless range info Aldy Hernandez
2017-06-16 8:00 ` Richard Biener
2017-06-23 9:02 ` Aldy Hernandez
[not found] ` <CAGm3qMXOYa3Km6FGiji0j2txeZJfyiLTR7V6EDMTDEDQo0RWBA@mail.gmail.com>
2017-06-23 10:24 ` Richard Biener
2017-06-23 10:32 ` Jakub Jelinek
2017-06-23 11:01 ` Richard Biener
2017-06-27 10:26 ` Aldy Hernandez
2017-06-27 10:38 ` Jakub Jelinek
2017-06-28 7:56 ` Aldy Hernandez
2017-06-29 9:53 ` Richard Biener
2017-08-02 13:29 ` Tom de Vries [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=aa8a659f-b201-5c42-1fe0-01947b21839a@mentor.com \
--to=tom_devries@mentor.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.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).