public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103195] New: tfft2 text grows by 70% with -Ofast between g:52fa771758635d9c53cddb9116e5a66fae592230...a97fdde627e64202940112009d45d17f85e4cc61
Date: Thu, 11 Nov 2021 17:44:13 +0000 [thread overview]
Message-ID: <bug-103195-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103195
Bug ID: 103195
Summary: tfft2 text grows by 70% with -Ofast between
g:52fa771758635d9c53cddb9116e5a66fae592230...a97fdde62
7e64202940112009d45d17f85e4cc61
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
This is seen at LTN here
https://lnt.opensuse.org/db_default/v4/CPP/24179
https://lnt.opensuse.org/db_default/v4/CPP/graph?highlight_run=24179&plot.0=14.799.4
and similarly on other testers. Performance is not improved so it looks like
bit extreme even for -Ofast. It would be nice to know why such growth happens.
next reply other threads:[~2021-11-11 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 17:44 hubicka at gcc dot gnu.org [this message]
2021-11-12 7:39 ` [Bug tree-optimization/103195] " rguenth at gcc dot gnu.org
2021-11-12 10:12 ` [Bug tree-optimization/103195] [12 Regression] tfft2 text grows by 70% with -Ofast since r12-5113-gd70ef65692fced7a marxin at gcc dot gnu.org
2021-11-12 10:27 ` hubicka at kam dot mff.cuni.cz
2021-11-12 21:25 ` hubicka at gcc dot gnu.org
2021-11-16 13:10 ` rguenth at gcc dot gnu.org
2022-01-18 14:29 ` rguenth at gcc dot gnu.org
2022-01-18 14:31 ` Jan Hubicka
2022-01-18 14:31 ` hubicka at kam dot mff.cuni.cz
2022-02-17 22:33 ` jamborm at gcc dot gnu.org
2022-05-06 8:31 ` [Bug tree-optimization/103195] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:10 ` 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-103195-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: 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).