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 11:25:44 +0000 [thread overview] Message-ID: <bug-113372-4-OLEKUsKQGT@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 #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ah, so it really is the classical stack conflicts vs. ADDR_EXPR problem. Before dom3 we have _2 = &bitint.6 + 8; ivtmp.40_3 = (unsigned long) _2; from ivopts above the loop using bitint.6 and _44 = &bitint.6 + 8; ivtmp.28_43 = (unsigned long) _44; above the second loop computing bitint.6, with bitint.6 ={v} {CLOBBER(eos)}; in between (or eob). dom3 optimizes the latter to _44 = &MEM <unsigned long[100]> [(void *)&bitint.6 + 8B]; ivtmp.28_43 = ivtmp.40_3; and later on all the visible uses of bitint.6 in the second part of the function after bitint.6 ={v} {CLOBBER(eos)}; disappear.
next prev parent reply other threads:[~2024-01-15 11:25 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 [this message] 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 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-OLEKUsKQGT@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).