From: Alan Modra <amodra@gmail.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: gcc-patches@gcc.gnu.org, DJ Delorie <dj@redhat.com>,
Ian Lance Taylor <ian@airs.com>
Subject: Re: ATTRIBUTE_NONSTRING
Date: Sat, 28 Apr 2018 06:46:00 -0000 [thread overview]
Message-ID: <20180428062531.GQ18288@bubble.grove.modra.org> (raw)
In-Reply-To: <alpine.BSF.2.20.16.1804271823490.97924@arjuna.pair.com>
On Fri, Apr 27, 2018 at 06:24:28PM -0400, Hans-Peter Nilsson wrote:
> On Fri, 27 Apr 2018, Alan Modra wrote:
>
> > This patch adds ATTRIBUTE_NONSTRING, which will be used to curb
> > -Wstringop-truncation warnings in binutils. OK to apply?
> >
> > * ansidecl.h (ATTRIBUTE_NONSTRING): Define.
> >
> > diff --git a/include/ansidecl.h b/include/ansidecl.h
> > index c11daff..ec5f34d 100644
> > --- a/include/ansidecl.h
> > +++ b/include/ansidecl.h
> > @@ -283,6 +283,15 @@ So instead we use the macro below and test it against specific values. */
> > # endif /* GNUC >= 4.9 */
> > #endif /* ATTRIBUTE_NO_SANITIZE_UNDEFINED */
> >
> > +/* Attribute 'nonstring' was valid as of gcc 8. */
> > +#ifndef ATTRIBUTE_NONSTRING
> > +# if GCC_VERSION >= 8000
> > +# define ATTRIBUTE_NONSTRING __attribute__ ((nonstring))
>
> Uglify nonstring (as __nonstring__)?
Yes, that would be better. I copied the immediately preceding
ATTRIBUTE_NO_SANITIZE_UNDEFINED without thinking.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2018-04-28 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 3:17 ATTRIBUTE_NONSTRING Alan Modra
2018-04-27 22:27 ` ATTRIBUTE_NONSTRING Hans-Peter Nilsson
2018-04-28 6:46 ` Alan Modra [this message]
2018-05-01 17:28 ` ATTRIBUTE_NONSTRING Jeff Law
2018-04-30 18:21 ` ATTRIBUTE_NONSTRING Pedro Alves
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=20180428062531.GQ18288@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=ian@airs.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).