public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112581] [14 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu (generated code hangs)
Date: Fri, 17 Nov 2023 09:26:21 +0000 [thread overview]
Message-ID: <bug-112581-4-laSpDmWu6d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112581-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112581
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> It might be one of the x86 specific target patches ...
I don't think so, these patches deal specifically with high registers, and:
$ grep %.h pr112581.s
finds none.
next prev parent reply other threads:[~2023-11-17 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 5:07 [Bug tree-optimization/112581] New: " zhendong.su at inf dot ethz.ch
2023-11-17 5:13 ` [Bug middle-end/112581] " pinskia at gcc dot gnu.org
2023-11-17 7:15 ` [Bug middle-end/112581] [14 Regression] " rguenth at gcc dot gnu.org
2023-11-17 9:26 ` ubizjak at gmail dot com [this message]
2023-11-17 11:16 ` [Bug middle-end/112581] [14 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu (generated code hangs) since r14-4661 jakub at gcc dot gnu.org
2023-11-17 22:41 ` pinskia at gcc dot gnu.org
2023-11-17 23:04 ` pinskia at gcc dot gnu.org
2023-11-17 23:14 ` pinskia at gcc dot gnu.org
2023-11-17 23:18 ` pinskia at gcc dot gnu.org
2023-11-17 23:25 ` pinskia at gcc dot gnu.org
2023-11-18 4:09 ` [Bug middle-end/112581] [14 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu (generated code hangs) since r14-4661 due to reassoc not handling maybe_undefs pinskia at gcc dot gnu.org
2023-12-21 21:07 ` pinskia at gcc dot gnu.org
2023-12-23 18:36 ` pinskia at gcc dot gnu.org
2024-01-10 17:11 ` cvs-commit at gcc dot gnu.org
2024-01-10 17:11 ` pinskia 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-112581-4-laSpDmWu6d@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: link
Be 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).