public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at parcs dot ath.cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60765] Function attributes ignored for pointer-to-member-function parameters
Date: Fri, 04 Apr 2014 23:18:00 -0000 [thread overview]
Message-ID: <bug-60765-4-wPVBfcfAX7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60765-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60765
--- Comment #1 from patrick at parcs dot ath.cx ---
Oops, that warning is because I am currently compiling with G++ 4.8, which
doesn't implement returns_nonnull. Here's a better test case:
$ cat this.cc
struct Foo;
void foo (void (Foo::*) () __attribute__ ((nonnull)));
void bar (void (*) () __attribute__ ((nonnull)));
$ g++ this.cc c
this.cc:3:52: warning: ‘nonnull’ attribute only applies to function types
[-Wattributes]
void foo (void (Foo::*) () __attribute__ ((nonnull)));
^
>From gcc-bugs-return-448345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 04 23:23:30 2014
Return-Path: <gcc-bugs-return-448345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16630 invoked by alias); 4 Apr 2014 23:23:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16615 invoked by uid 48); 4 Apr 2014 23:23:26 -0000
From: "patrick at parcs dot ath.cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60764] Bogus -Wnonnull warning against constructors declared with __attribute__ ((nonnull(1)))
Date: Fri, 04 Apr 2014 23:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: patrick at parcs dot ath.cx
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60764-4-XvjCHMfOTx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-04/txt/msg00365.txt.bz2
Content-length: 132
http://gcc.gnu.org/bugzilla/show_bug.cgi?id`764
--- Comment #1 from patrick at parcs dot ath.cx ---
I will try to resolve this.
next prev parent reply other threads:[~2014-04-04 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 23:11 [Bug c++/60765] New: " patrick at parcs dot ath.cx
2014-04-04 23:18 ` patrick at parcs dot ath.cx [this message]
2014-04-04 23:23 ` [Bug c++/60765] " patrick at parcs dot ath.cx
2014-04-16 20:18 ` paolo at gcc dot gnu.org
2014-04-16 20:19 ` paolo.carlini at oracle dot com
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=bug-60765-4-wPVBfcfAX7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).