public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113287] wrong code with __builtin_mul_overflow_p() and _BitInt() with -O3 -msse4 Date: Sat, 13 Jan 2024 09:48:21 +0000 [thread overview] Message-ID: <bug-113287-4-MzhN0aCJJx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113287-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113287 --- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7012a252528233ca3ced5b9230013c50b604da9b commit r14-7223-g7012a252528233ca3ced5b9230013c50b604da9b Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Jan 13 10:46:51 2024 +0100 testsuite: Fix up vect-early-break_100-pr113287.c testcase [PR113287] When the testcase was being adjusted for unsigned long -> unsigned long long, two spots using long weren't changed to long long, so the testcase still warns about UB in shifts. 2024-01-13 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/113287 * gcc.dg/vect/vect-early-break_100-pr113287.c: Use long long instead of long.
prev parent reply other threads:[~2024-01-13 9:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-09 5:30 [Bug rtl-optimization/113287] New: " zsojka at seznam dot cz 2024-01-09 14:12 ` [Bug rtl-optimization/113287] " jakub at gcc dot gnu.org 2024-01-09 14:23 ` jakub at gcc dot gnu.org 2024-01-09 14:29 ` tnfchris at gcc dot gnu.org 2024-01-09 16:07 ` tnfchris at gcc dot gnu.org 2024-01-10 12:36 ` [Bug tree-optimization/113287] " tnfchris at gcc dot gnu.org 2024-01-10 14:32 ` cvs-commit at gcc dot gnu.org 2024-01-10 14:33 ` tnfchris at gcc dot gnu.org 2024-01-12 15:33 ` cvs-commit at gcc dot gnu.org 2024-01-13 9:48 ` cvs-commit 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-113287-4-MzhN0aCJJx@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).