public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94092] Code size and performance degradations after -ftree-loop-distribute-patterns was enabled at -O[2s]+
Date: Mon, 09 Mar 2020 06:29:38 +0000 [thread overview]
Message-ID: <bug-94092-4-2AqZHAkFqd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94092-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94092
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> >For coremark, this is not only harmful to performance, but also code size.
>
>
> Bad, very bad benchmark ....
Coremark only handles very very small data sets by default. I think you should
run your real code over this and see if it improves or not.
Also -O2 does not care exactly about code size, that -Os only.
Can you provide a test where besides coremark which decreases in performance
and increase in size?
next prev parent reply other threads:[~2020-03-09 6:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 6:06 [Bug tree-optimization/94092] New: " bina2374 at gmail dot com
2020-03-09 6:17 ` [Bug tree-optimization/94092] " pinskia at gcc dot gnu.org
2020-03-09 6:29 ` pinskia at gcc dot gnu.org [this message]
2020-03-09 6:30 ` pinskia at gcc dot gnu.org
2020-03-09 7:37 ` glisse at gcc dot gnu.org
2020-03-09 9:48 ` rguenth at gcc dot gnu.org
2021-02-19 8:05 ` aoliva at gcc dot gnu.org
2021-02-23 23:57 ` wilson at gcc dot gnu.org
2021-02-24 7:43 ` rguenth at gcc dot gnu.org
2021-02-24 9:05 ` bina2374 at gmail dot com
2021-02-24 9:20 ` rguenth at gcc dot gnu.org
2021-02-26 6:35 ` bina2374 at gmail dot com
2021-03-03 6:30 ` bina2374 at gmail dot com
2021-03-03 8:03 ` rguenther at suse dot de
2021-04-29 4:24 ` aoliva at gcc dot gnu.org
2021-04-30 14:38 ` law at gcc dot gnu.org
2021-05-03 6:28 ` rguenther at suse dot de
2021-05-04 12:26 ` 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-94092-4-2AqZHAkFqd@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).