From: James Youngman <james@youngman.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: Correct but unhelpful VLA warning vs. gnulib's gettext.h; can we eliminate the false positive?
Date: Mon, 11 Jul 2011 02:02:40 +0100 [thread overview]
Message-ID: <CAGwX767_35jnwPwbL3DUfYvgm1EkejZiXwLtxcSBPqyLCWs4fA@mail.gmail.com> (raw)
In-Reply-To: <4E1A3FA5.2030403@cs.ucla.edu>
On Mon, Jul 11, 2011 at 1:11 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 07/10/11 02:16, James Youngman wrote:
>> A function-level pragma would probably be ideal here, but
>> unfortunately they can only be used to tweak optimisation and function
>> attributes.
>
> Can you do "#pragma GCC diagnostic push" at the start of the function,
> and "#pragma GCC diagnostic pop" at the end? That's *supposed* to
> work (not that I've tried it....).
I'll try it next week. It's not documented in the GCC-4.4 Texinfo
manual, though; perhaps it's a recent introduction.
James.
next prev parent reply other threads:[~2011-07-11 1:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 22:32 Correct but unhelpful VLA warning vs. gnulib's gettext.h; can we eliminate the false positive? James Youngman
2011-07-10 4:47 ` Paul Eggert
2011-07-10 9:16 ` James Youngman
2011-07-11 0:11 ` Paul Eggert
2011-07-11 1:02 ` James Youngman [this message]
2011-07-11 1:13 ` Paul Eggert
2011-07-10 9:48 ` Simon Josefsson
2019-01-14 6:10 ` Pádraig Brady
2019-01-15 1:57 ` VLA and alloca Bruno Haible
2019-01-20 4:46 ` Pádraig Brady
2019-01-20 10:19 ` Bruno Haible
2019-01-20 21:03 ` Pádraig Brady
2019-02-02 22:44 ` Paul Eggert
2019-01-20 15:36 ` Bruno Haible
2019-01-24 11:51 ` Tim Rühsen
2019-02-02 22:58 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGwX767_35jnwPwbL3DUfYvgm1EkejZiXwLtxcSBPqyLCWs4fA@mail.gmail.com \
--to=james@youngman.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).