From: Andreas Schwab <schwab@linux-m68k.org>
To: Martin Sebor <msebor@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] adding missing LTO to some warning options (PR 78606)
Date: Fri, 13 Jan 2017 18:49:00 -0000 [thread overview]
Message-ID: <87lguebxsd.fsf@linux-m68k.org> (raw)
In-Reply-To: <06c24069-90af-5778-52a2-c9167eb109ab@gmail.com> (Martin Sebor's message of "Tue, 10 Jan 2017 15:16:03 -0700")
On Jan 10 2017, Martin Sebor <msebor@gmail.com> wrote:
> Index: gcc/testsuite/gcc.dg/pr78768.c
> ===================================================================
> --- gcc/testsuite/gcc.dg/pr78768.c (revision 0)
> +++ gcc/testsuite/gcc.dg/pr78768.c (working copy)
> @@ -0,0 +1,13 @@
> +/* PR c/78768 - -Walloca-larger-than and -Wformat-length warnings disabled
> + by -flto
> + { dg-do run }
> + { dg-options "-O2 -Walloca-larger-than=10 -Wformat -Wformat-length -flto" } */
> +
> +int main (void)
> +{
> + char *d = (char *)__builtin_alloca (12); /* { dg-warning "argument to .alloca. is too large" } */
> +
> + __builtin_sprintf (d, "%32s", "x"); /* { dg-warning "directive writing 32 bytes into a region of size 12" "-Wformat-length" { xfail *-*-* } } */
> +
> + return 0;
> +}
Why is that a run test? It cannot be usefully executed.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-01-13 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 22:16 Martin Sebor
2017-01-11 8:21 ` Richard Biener
2017-01-13 18:49 ` Andreas Schwab [this message]
2017-01-17 12:04 ` Kyrill Tkachov
2017-01-17 16:45 ` Martin Sebor
2017-04-30 23:39 ` Tom de Vries
2017-05-01 18:05 ` Martin Sebor
2017-05-02 10:22 ` Tom de Vries
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=87lguebxsd.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
--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).