public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/39464] [4.6/4.7/4.8 Regression] Attribute may_alias causes invalid warning Date: Thu, 06 Dec 2012 18:21:00 -0000 [thread overview] Message-ID: <bug-39464-4-TdP95V0DC1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-39464-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39464 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |jsm28 at gcc dot gnu.org --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-06 18:21:09 UTC --- In any case, I'd limit the /* If there is a mismatch, do warn. */ else if (warn_pointer_sign) WARN_FOR_ASSIGNMENT (location, OPT_Wpointer_sign, G_("pointer targets in passing argument " "%d of %qE differ in signedness"), G_("pointer targets in assignment " "differ in signedness"), G_("pointer targets in initialization " "differ in signedness"), G_("pointer targets in return differ " "in signedness")); warning to actual sign differences only, i.e.
next prev parent reply other threads:[~2012-12-06 18:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-39464-4@http.gcc.gnu.org/bugzilla/> 2011-06-27 15:20 ` [Bug c/39464] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2012-03-13 15:47 ` [Bug c/39464] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org 2012-07-02 12:16 ` rguenth at gcc dot gnu.org 2012-12-06 18:21 ` jakub at gcc dot gnu.org [this message] 2012-12-06 18:27 ` [Bug c/39464] [4.6/4.7/4.8 " jakub at gcc dot gnu.org 2012-12-06 19:29 ` pinskia at gcc dot gnu.org 2012-12-07 10:05 ` jakub at gcc dot gnu.org 2012-12-07 16:42 ` jakub at gcc dot gnu.org 2012-12-18 22:48 ` jakub at gcc dot gnu.org 2012-12-19 9:12 ` jakub at gcc dot gnu.org 2012-12-20 10:40 ` jakub at gcc dot gnu.org
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-39464-4-TdP95V0DC1@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: linkBe 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).