From: Christophe Lyon <christophe.lyon@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Aldy Hernandez <aldyh@redhat.com>, Jeff Law <law@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING: new pass to warn on questionable uses of alloca() and VLAs
Date: Wed, 19 Oct 2016 10:50:00 -0000 [thread overview]
Message-ID: <CAKdteOYM32Y1N9LehyzKRXMYxdZxyn6hL_+x=7i-JfXDqRAypA@mail.gmail.com> (raw)
In-Reply-To: <mvmpomwpqgk.fsf@hawking.suse.de>
On 19 October 2016 at 12:45, Andreas Schwab <schwab@suse.de> wrote:
> FAIL: gcc.dg/Walloca-1.c (test for warnings, line 26)
> FAIL: gcc.dg/Walloca-1.c (test for excess errors)
> Excess errors:
> /daten/aranym/gcc/gcc-20161019/gcc/testsuite/gcc.dg/Walloca-1.c:26:5: warning: unbounded use of 'alloca' [-Walloca-larger-than=]
> FAIL: gcc.dg/Walloca-2.c (test for warnings, line 34)
> FAIL: gcc.dg/Walloca-2.c note (test for warnings, line 34)
> FAIL: gcc.dg/Walloca-2.c (test for excess errors)
> Excess errors:
> /daten/aranym/gcc/gcc-20161019/gcc/testsuite/gcc.dg/Walloca-2.c:11:7: warning: unbounded use of 'alloca' [-Walloca-larger-than=]
> /daten/aranym/gcc/gcc-20161019/gcc/testsuite/gcc.dg/Walloca-2.c:34:9: warning: unbounded use of 'alloca' [-Walloca-larger-than=]
>
I'm seeing the same errors on arm* targets.
Christophe
> Andreas.
>
> --
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."
next prev parent reply other threads:[~2016-10-19 10:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 9:01 Aldy Hernandez
2016-07-27 9:26 ` Rainer Orth
2016-08-04 16:38 ` Jeff Law
[not found] ` <57B6D2F1.6050709@redhat.com>
2016-08-19 14:57 ` Aldy Hernandez
2016-08-19 14:59 ` Aldy Hernandez
2016-09-13 20:30 ` Jeff Law
2016-10-18 21:42 ` Aldy Hernandez
2016-10-19 7:08 ` Eric Botcazou
2016-10-19 12:46 ` Aldy Hernandez
2016-10-19 13:24 ` Eric Botcazou
2016-10-19 13:27 ` Aldy Hernandez
2016-10-19 13:42 ` Eric Botcazou
2016-10-19 13:54 ` Aldy Hernandez
2016-10-19 15:32 ` Eric Botcazou
2016-10-19 10:45 ` Andreas Schwab
2016-10-19 10:50 ` Christophe Lyon [this message]
2016-10-19 12:54 ` Aldy Hernandez
2016-10-19 13:03 ` Andreas Schwab
2016-10-19 13:16 ` Eric Botcazou
2016-10-19 15:32 ` Aldy Hernandez
2016-10-19 15:38 ` Andreas Schwab
2016-10-19 15:42 ` Eric Botcazou
2016-10-19 15:55 ` Jeff Law
2016-10-19 16:22 ` Christophe Lyon
2016-10-19 18:43 ` Aldy Hernandez
2016-10-19 20:16 ` Christophe Lyon
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='CAKdteOYM32Y1N9LehyzKRXMYxdZxyn6hL_+x=7i-JfXDqRAypA@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=schwab@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).