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 middle-end/94412] wrong code with -fsanitize=undefined and vectors Date: Mon, 30 Mar 2020 20:50:50 +0000 [thread overview] Message-ID: <bug-94412-4-YESRZCzxfB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94412 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah, -1U / 11 is 390451572, not 0. 11149 /* Convert -A / -B to A / B when the type is signed and overflow is 11150 undefined. */ 11151 if ((!INTEGRAL_TYPE_P (type) || TYPE_OVERFLOW_UNDEFINED (type)) 11152 && TREE_CODE (op0) == NEGATE_EXPR 11153 && negate_expr_p (op1)) needs to be adjusted the way Marc said.
next prev parent reply other threads:[~2020-03-30 20:50 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-30 20:10 [Bug middle-end/94412] New: " zsojka at seznam dot cz 2020-03-30 20:41 ` [Bug middle-end/94412] " glisse at gcc dot gnu.org 2020-03-30 20:50 ` jakub at gcc dot gnu.org [this message] 2020-03-30 21:15 ` jakub at gcc dot gnu.org 2020-03-31 6:38 ` zsojka at seznam dot cz 2020-03-31 7:38 ` [Bug middle-end/94412] [8/9/10 Regression] wrong code with vectors jakub at gcc dot gnu.org 2020-03-31 9:07 ` cvs-commit at gcc dot gnu.org 2020-03-31 9:11 ` [Bug middle-end/94412] [8/9 " jakub at gcc dot gnu.org 2020-04-07 19:04 ` cvs-commit at gcc dot gnu.org 2020-04-07 20:02 ` [Bug middle-end/94412] [8 " jakub at gcc dot gnu.org 2020-09-17 17:24 ` 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-94412-4-YESRZCzxfB@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).