public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60517] warning/error for taking address of member of a temporary object Date: Fri, 14 Mar 2014 17:29:00 -0000 [thread overview] Message-ID: <bug-60517-4-HBeG2eLtkU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60517-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60517 --- Comment #8 from Marc Glisse <glisse at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #7) > To avoid duplicates, the front-end could just return something else, like > NULL, when it detects this case (I guess the behavior is undefined and we > can do whatever we want, no?). I guess... Then we might as well introduce a call to __builtin_unreachable right before the return, at the same time as we replace the return value. >From gcc-bugs-return-446313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 17:32:47 2014 Return-Path: <gcc-bugs-return-446313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21898 invoked by alias); 14 Mar 2014 17:32:47 -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 21863 invoked by uid 55); 14 Mar 2014 17:32:44 -0000 From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/60523] Warning flag for octal literals Date: Fri, 14 Mar 2014 17:32: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: joseph at codesourcery dot com 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-60523-4-AzHLsp5JWS@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60523-4@http.gcc.gnu.org/bugzilla/> References: <bug-60523-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-03/txt/msg01182.txt.bz2 Content-length: 544 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`523 --- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Octal literals are also used in macro definitions from system headers, so care would be needed that a warning doesn't apply to those. Such a warning should of course not apply to 0 (and maybe more generally should not apply to any octal constant consisting of some number of leading 0s followed by at most one nonzero digit, as those have the same value whether interpreted as octal or as decimal).
next prev parent reply other threads:[~2014-03-14 17:29 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-13 15:54 [Bug c++/60517] New: " manu at gcc dot gnu.org 2014-03-13 20:42 ` [Bug c++/60517] " glisse at gcc dot gnu.org 2014-03-13 23:44 ` manu at gcc dot gnu.org 2014-03-14 7:19 ` glisse at gcc dot gnu.org 2014-03-14 10:41 ` manu at gcc dot gnu.org 2014-03-14 12:13 ` glisse at gcc dot gnu.org 2014-03-14 15:41 ` glisse at gcc dot gnu.org 2014-03-14 16:51 ` manu at gcc dot gnu.org 2014-03-14 17:29 ` glisse at gcc dot gnu.org [this message] 2014-03-14 18:02 ` glisse at gcc dot gnu.org 2014-04-05 23:01 ` glisse at gcc dot gnu.org 2014-04-06 8:23 ` glisse at gcc dot gnu.org 2014-04-06 10:17 ` glisse at gcc dot gnu.org 2014-06-26 17:22 ` paolo.carlini at oracle dot com 2014-07-31 9:34 ` glisse at gcc dot gnu.org 2014-08-22 13:02 ` manu at gcc dot gnu.org 2014-08-22 13:22 ` glisse at gcc dot gnu.org 2014-11-22 14:48 ` glisse 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-60517-4-HBeG2eLtkU@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).