public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/96549] [10/11 Regression] Wrong evaluation of a comparison between long & short Date: Mon, 10 Aug 2020 08:09:44 +0000 [thread overview] Message-ID: <bug-96549-4-7tPvwIAt8c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96549 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |jakub at gcc dot gnu.org, | |marxin at gcc dot gnu.org Last reconfirmed| |2020-08-10 Summary|Wrong evaluation of a |[10/11 Regression] Wrong |comparison between long & |evaluation of a comparison |short |between long & short --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Thank you for the report! Slighly modified test-case: long c = -1L; long b = 0L; int main(void) { if (3L > (short) ((c ^= (b = 1L)) * 3L)) return 0; __builtin_abort (); } Started with r10-7921-gbca558de2a24b2a7.
next prev parent reply other threads:[~2020-08-10 8:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-10 8:03 [Bug c/96549] New: " zhige.yu18 at imperial dot ac.uk 2020-08-10 8:09 ` marxin at gcc dot gnu.org [this message] 2020-08-10 8:20 ` [Bug middle-end/96549] " pinskia at gcc dot gnu.org 2020-08-10 8:20 ` [Bug middle-end/96549] [10/11 Regression] " pinskia at gcc dot gnu.org 2020-08-10 9:10 ` jakub at gcc dot gnu.org 2020-08-10 9:13 ` jakub at gcc dot gnu.org 2020-08-11 11:52 ` cvs-commit at gcc dot gnu.org 2020-08-11 11:53 ` [Bug middle-end/96549] [10 " jakub at gcc dot gnu.org 2020-08-25 8:12 ` rguenth at gcc dot gnu.org 2020-08-25 17:45 ` cvs-commit at gcc dot gnu.org 2020-08-25 18:23 ` 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-96549-4-7tPvwIAt8c@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).