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 tree-optimization/113372] wrong code with _BitInt() arithmetics at -O1 Date: Mon, 15 Jan 2024 14:35:51 +0000 [thread overview] Message-ID: <bug-113372-4-xcOfflSjOp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113372-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113372 --- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 57085 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57085&action=edit gcc14-pr113372.patch The non-propagation workaround which seems to fix^H^H^Hworkaround all those 4 issues (PR90348 testcase actually doesn't FAIL anymore, but I've verified the patch results in in and buf no longer being shared) can look like this.
next prev parent reply other threads:[~2024-01-15 14:35 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 8:53 [Bug tree-optimization/113372] New: " zsojka at seznam dot cz 2024-01-13 9:03 ` [Bug tree-optimization/113372] " pinskia at gcc dot gnu.org 2024-01-15 10:28 ` jakub at gcc dot gnu.org 2024-01-15 10:33 ` jakub at gcc dot gnu.org 2024-01-15 11:25 ` jakub at gcc dot gnu.org 2024-01-15 11:31 ` rguenther at suse dot de 2024-01-15 11:51 ` jakub at gcc dot gnu.org 2024-01-15 12:07 ` jakub at gcc dot gnu.org 2024-01-15 12:19 ` rguenth at gcc dot gnu.org 2024-01-15 12:43 ` jakub at gcc dot gnu.org 2024-01-15 12:55 ` jakub at gcc dot gnu.org 2024-01-15 13:04 ` rguenth at gcc dot gnu.org 2024-01-15 13:35 ` jakub at gcc dot gnu.org 2024-01-15 13:47 ` rguenther at suse dot de 2024-01-15 14:35 ` jakub at gcc dot gnu.org [this message] 2024-01-15 14:42 ` rguenth at gcc dot gnu.org 2024-01-15 14:43 ` matz at gcc dot gnu.org 2024-01-15 14:58 ` jakub at gcc dot gnu.org 2024-01-16 7:21 ` rguenther at suse dot de 2024-01-16 10:51 ` cvs-commit at gcc dot gnu.org 2024-01-16 10:56 ` jakub at gcc dot gnu.org 2024-01-20 17:09 ` pinskia at gcc dot gnu.org 2024-03-02 0:38 ` cvs-commit at gcc dot gnu.org 2024-03-28 11:01 ` 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-113372-4-xcOfflSjOp@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).