public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/68052] No printf format warnings in C++ code for macro in system headers Date: Fri, 23 Oct 2015 09:23:00 -0000 [thread overview] Message-ID: <bug-68052-4-ZarlaKPQOc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68052-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68052 --- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Olivier Blin from comment #3) > Quoting Martin Sebor's answer from the gcc-help mailing list: > https://gcc.gnu.org/ml/gcc-help/2015-10/msg00128.html What Martin describes there is a different bug that occurs when there is a whole stack of macro expansions (which is not the case in the original testcase). My guess is that it is https://gcc.gnu.org/PR52998 Most of the bugs in the macro unwinder are known and triaged, but no one has stepped up to fix them. See I) at https://gcc.gnu.org/wiki/Better_Diagnostics >From gcc-bugs-return-500376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Oct 23 09:35:42 2015 Return-Path: <gcc-bugs-return-500376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 70103 invoked by alias); 23 Oct 2015 09:35:41 -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 70079 invoked by uid 48); 23 Oct 2015 09:35:37 -0000 From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/68067] Wrong constant folding Date: Fri, 23 Oct 2015 09:35: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: trans-mem X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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-68067-4-TxOx53PPqv@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-68067-4@http.gcc.gnu.org/bugzilla/> References: <bug-68067-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: 2015-10/txt/msg01931.txt.bz2 Content-length: 315 https://gcc.gnu.org/bugzilla/show_bug.cgi?idh067 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Yep. Btw, what happens is that we see if (tem - 1 != 2147483647) and that is obviously always true unless tem - 1 wraps from -2147483648 to 2147483647 which would invoke undefined behavior.
prev parent reply other threads:[~2015-10-23 9:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-22 17:10 [Bug c++/68052] New: " gcc at blino dot org 2015-10-22 22:10 ` [Bug c++/68052] " gcc at blino dot org 2015-10-22 22:13 ` gcc at blino dot org 2015-10-23 9:19 ` manu at gcc dot gnu.org 2015-10-23 9:23 ` manu at gcc dot gnu.org [this message]
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-68052-4-ZarlaKPQOc@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).