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 middle-end/61677] False positive with -Wmaybe-uninitialized (test case included) Date: Thu, 03 Jul 2014 15:26:00 -0000 [thread overview] Message-ID: <bug-61677-4-v69wr6J9yi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61677-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61677 --- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- Perhaps related to PR61409 or PR56574. >From gcc-bugs-return-455584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jul 03 15:34:07 2014 Return-Path: <gcc-bugs-return-455584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 19703 invoked by alias); 3 Jul 2014 15:34:06 -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 19624 invoked by uid 48); 3 Jul 2014 15:33:56 -0000 From: "wmichaelv at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/61689] Assignment and Operator not working as intended. Date: Thu, 03 Jul 2014 15:34: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.7.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wmichaelv at hotmail dot com X-Bugzilla-Status: RESOLVED 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-61689-4-7eaKGK4QkE@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61689-4@http.gcc.gnu.org/bugzilla/> References: <bug-61689-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-07/txt/msg00175.txt.bz2 Content-length: 461 https://gcc.gnu.org/bugzilla/show_bug.cgi?ida689 --- Comment #2 from wmichaelv at hotmail dot com --- (In reply to Marek Polacek from comment #1) > The program has undefined behaviour; an assignment is not a sequence point. > See what -Wsequence-point says. According to the order operation, grouping should be calculated first before add, subtract, division, and multiplication, and assignment. And the associativity of assignment is from right to left.
next prev parent reply other threads:[~2014-07-03 15:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-02 22:24 [Bug c/61677] New: " josh at joshtriplett dot org 2014-07-03 6:51 ` [Bug middle-end/61677] " schwab@linux-m68k.org 2014-07-03 15:17 ` manu at gcc dot gnu.org 2014-07-03 15:26 ` manu at gcc dot gnu.org [this message] 2021-03-29 21:23 ` [Bug middle-end/61677] False positive with -Wmaybe-uninitialized (predicate analysis, VRP) cvs-commit at gcc dot gnu.org 2021-03-29 21:29 ` msebor at gcc dot gnu.org 2022-08-29 14:26 ` [Bug tree-optimization/61677] " rguenth 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-61677-4-v69wr6J9yi@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).