public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@kam.mff.cuni.cz>
To: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug tree-optimization/103300] New: wrong code at -O3 on x86_64-linux-gnu
Date: Wed, 17 Nov 2021 12:08:52 +0100 [thread overview]
Message-ID: <20211117110852.GD87060@kam.mff.cuni.cz> (raw)
In-Reply-To: <bug-103300-4@http.gcc.gnu.org/bugzilla/>
Needs -O2 -floop-unroll-and-jam --param early-inlining-insns=14
to fail, so I guess it may be issue with unrol-and-jam.
next prev parent reply other threads:[~2021-11-17 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:17 zhendong.su at inf dot ethz.ch
2021-11-17 10:24 ` [Bug tree-optimization/103300] [12 Regression] " pinskia at gcc dot gnu.org
2021-11-17 11:08 ` Jan Hubicka [this message]
2021-11-17 11:08 ` hubicka at kam dot mff.cuni.cz
2021-11-17 22:32 ` pinskia at gcc dot gnu.org
2021-11-18 7:47 ` rguenth at gcc dot gnu.org
2021-11-18 10:37 ` rguenth at gcc dot gnu.org
2021-11-18 10:39 ` [Bug tree-optimization/103300] [12 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-4526-gd8edfadfc7a9795b marxin at gcc dot gnu.org
2021-12-02 7:22 ` zhendong.su at inf dot ethz.ch
2021-12-02 9:14 ` marxin at gcc dot gnu.org
2022-02-15 12:53 ` 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=20211117110852.GD87060@kam.mff.cuni.cz \
--to=hubicka@kam.mff.cuni.cz \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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).