public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/110391] New: wrong code at -O2 and -O3 with "on x86_64-linux-gnu Date: Sat, 24 Jun 2023 13:17:52 +0000 [thread overview] Message-ID: <bug-110391-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110391 Bug ID: 110391 Summary: wrong code at -O2 and -O3 with "on x86_64-linux-gnu Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zhendong.su at inf dot ethz.ch Target Milestone: ---
next reply other threads:[~2023-06-24 13:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-24 13:17 zhendong.su at inf dot ethz.ch [this message] 2023-06-24 13:20 ` [Bug rtl-optimization/110391] wrong code at -O2 and -O3 with "-fsel-sched-pipelining -fselective-scheduling2" on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2023-06-24 15:23 ` [Bug rtl-optimization/110391] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-26 9:12 ` zhendong.su at inf dot ethz.ch 2023-06-29 9:18 ` zhendong.su at inf dot ethz.ch 2023-06-29 17:33 ` zhendong.su at inf dot ethz.ch 2024-03-04 1:49 ` law 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-110391-4@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).