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 middle-end/112600] Failed to optimize saturating addition using __builtin_add_overflow Date: Thu, 06 Jun 2024 17:45:41 +0000 [thread overview] Message-ID: <bug-112600-4-TH7UKM6xFT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112600-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112600 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:366d45c8d4911dc7874d2e64cf2583c0133b8dd5 commit r15-1077-g366d45c8d4911dc7874d2e64cf2583c0133b8dd5 Author: Uros Bizjak <ubizjak@gmail.com> Date: Thu Jun 6 19:18:41 2024 +0200 testsuite/i386: Add vector sat_sub testcases [PR112600] PR middle-end/112600 gcc/testsuite/ChangeLog: * gcc.target/i386/pr112600-2a.c: New test. * gcc.target/i386/pr112600-2b.c: New test.
next prev parent reply other threads:[~2024-06-06 17:45 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-17 21:40 [Bug middle-end/112600] New: " redi at gcc dot gnu.org 2023-11-17 21:41 ` [Bug middle-end/112600] " redi at gcc dot gnu.org 2023-11-17 21:45 ` redi at gcc dot gnu.org 2023-11-19 21:43 ` pinskia at gcc dot gnu.org 2023-11-20 9:23 ` rguenth at gcc dot gnu.org 2024-01-22 12:46 ` tnfchris at gcc dot gnu.org 2024-05-16 12:09 ` cvs-commit at gcc dot gnu.org 2024-05-16 12:09 ` cvs-commit at gcc dot gnu.org 2024-05-17 14:57 ` cvs-commit at gcc dot gnu.org 2024-05-18 2:17 ` cvs-commit at gcc dot gnu.org 2024-06-05 8:38 ` cvs-commit at gcc dot gnu.org 2024-06-05 20:42 ` ubizjak at gmail dot com 2024-06-06 17:45 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-08 10:19 ` cvs-commit at gcc dot gnu.org 2024-06-09 10:10 ` cvs-commit at gcc dot gnu.org 2024-06-11 16:59 ` cvs-commit 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-112600-4-TH7UKM6xFT@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).