public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110243] [13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu Date: Wed, 21 Jun 2023 13:50:06 +0000 [thread overview] Message-ID: <bug-110243-4-2aGjZPqUFT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110243-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110243 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- There's now a single strip_offset left in IVOPTs, the problematic one. That one isn't trivial to convert to split_constant_offset since that only deals with pointer or sizetype quantities in a way that's reasonable for this place. There's the opportunity to generalize split_constant_offset to work on other (unsigned) "base" types. I think that's the most reasonable thing to do.
next prev parent reply other threads:[~2023-06-21 13:50 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-13 21:10 [Bug c/110243] New: " shaohua.li at inf dot ethz.ch 2023-06-13 21:26 ` [Bug tree-optimization/110243] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-14 12:13 ` rguenth at gcc dot gnu.org 2023-06-16 11:32 ` rguenth at gcc dot gnu.org 2023-06-16 11:43 ` rguenth at gcc dot gnu.org 2023-06-21 13:50 ` rguenth at gcc dot gnu.org [this message] 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-07-30 14:35 ` shaohua.li at inf dot ethz.ch 2023-07-31 7:14 ` rguenth at gcc dot gnu.org 2023-10-17 14:35 ` [Bug tree-optimization/110243] [13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu since r13-3875-g9e11ceef165 rguenth at gcc dot gnu.org 2023-10-20 13:15 ` cvs-commit at gcc dot gnu.org 2023-10-20 13:16 ` [Bug tree-optimization/110243] [13 " rguenth at gcc dot gnu.org 2023-10-20 13:50 ` rguenth at gcc dot gnu.org 2023-10-20 13:54 ` cvs-commit at gcc dot gnu.org 2023-10-20 13:55 ` [Bug tree-optimization/110243] [12/13 " rguenth at gcc dot gnu.org 2023-10-20 13:57 ` rguenth at gcc dot gnu.org 2023-10-20 13:58 ` rguenth at gcc dot gnu.org 2024-02-06 13:21 ` rguenth 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-110243-4-2aGjZPqUFT@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).