public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/95123] [10/11/12 Regression] Wrong code w/ -O2 -fselective-scheduling2 -funroll-loops --param early-inlining-insns=5 --param loop-invariant-max-bbs-in-loop=3 --param max-jump-thread-duplication-stmts=0 -fPIE
Date: Mon, 31 Jan 2022 09:04:06 +0000 [thread overview]
Message-ID: <bug-95123-4-7j46TOPfRw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95123-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95123
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
--- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #11)
> Seems to be working on the trunk, would be interesting to see why it passes
> there.
Fixed with r12-4240-g2b8453c401b699ed and it still crashes with
-fno-tree-vectorize on master.
next prev parent reply other threads:[~2022-01-31 9:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 8:20 [Bug rtl-optimization/95123] New: [10/11 Regression] Wrong code w/ -O2 -fselective-scheduling2 -funroll-loops --param early-inlining-insns=5 --param loop-invariant-max-bbs-in-loop=3 --param max-jump-thread-duplication-stmts=0 asolokha at gmx dot com
2020-05-14 9:53 ` [Bug rtl-optimization/95123] " amonakov at gcc dot gnu.org
2020-05-14 10:16 ` marxin at gcc dot gnu.org
2020-05-14 10:33 ` asolokha at gmx dot com
2020-05-14 10:35 ` asolokha at gmx dot com
2020-05-14 10:39 ` asolokha at gmx dot com
2020-05-14 10:41 ` amonakov at gcc dot gnu.org
2020-05-14 10:47 ` asolokha at gmx dot com
2020-05-14 11:11 ` marxin at gcc dot gnu.org
2020-05-14 11:57 ` rguenth at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2021-01-14 8:48 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-01-30 0:26 ` [Bug rtl-optimization/95123] [10/11/12 Regression] Wrong code w/ -O2 -fselective-scheduling2 -funroll-loops --param early-inlining-insns=5 --param loop-invariant-max-bbs-in-loop=3 --param max-jump-thread-duplication-stmts=0 -fPIE pinskia at gcc dot gnu.org
2022-01-31 9:04 ` marxin at gcc dot gnu.org [this message]
2022-06-28 10:40 ` [Bug rtl-optimization/95123] [10/11/12/13 " jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug rtl-optimization/95123] [11/12/13/14 " 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-95123-4-7j46TOPfRw@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).