public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54063] [4.8 regression] on powerpc64 gcc 4.8 generates larger code for global variable accesses than gcc 4.7
Date: Tue, 04 Dec 2012 13:05:00 -0000 [thread overview]
Message-ID: <bug-54063-4-m8GU6TxX2P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54063-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54063
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-04 13:05:05 UTC ---
While the memory load is split already during reload, the set for &head is only
split during split2 pass, which is after postreload_cse (and gcse2) which are
the last CSE-ish passes I think. So perhaps you could tweak machine reorg pass
to handle some of the easy cases, or what exactly is the reason for running
split2 after postreload CSE instead of before it?
next prev parent reply other threads:[~2012-12-04 13:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 12:05 [Bug target/54063] New: " mikpe at it dot uu.se
2012-07-21 18:47 ` [Bug target/54063] " mikpe at it dot uu.se
2012-07-23 2:14 ` amodra at gmail dot com
2012-07-23 8:27 ` rguenth at gcc dot gnu.org
2012-09-19 13:57 ` rguenth at gcc dot gnu.org
2012-12-04 13:05 ` jakub at gcc dot gnu.org [this message]
2013-03-22 14:44 ` [Bug target/54063] [4.8/4.9 regression] on powerpc64 gcc 4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-10-16 9:49 ` jakub at gcc dot gnu.org
2013-10-25 11:10 ` rguenth at gcc dot gnu.org
2014-05-22 9:03 ` [Bug target/54063] [4.8/4.9/4.10 regression] on powerpc64 gcc 4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:25 ` [Bug target/54063] [4.8/4.9/5 regression] on powerpc64 gcc 4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-24 18:47 ` steven at gcc dot gnu.org
2015-06-23 8:17 ` [Bug target/54063] [4.8/4.9/5/6 regression] on powerpc64 gcc 4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:55 ` [Bug target/54063] [4.9/5/6 regression] on powerpc64 gcc 4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:27 ` jakub at gcc dot gnu.org
2020-03-12 11:58 ` [Bug target/54063] [8/9/10 regression] on powerpc64 gcc 4.9/8 " jakub at gcc dot gnu.org
2021-06-01 8:05 ` [Bug target/54063] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-11-30 14:38 ` roger at nextmovesoftware dot com
2021-11-30 17:00 ` segher at gcc dot gnu.org
2022-05-27 9:34 ` [Bug target/54063] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-04-20 8:46 ` [Bug target/54063] [10/11/12/13/14 " guihaoc at gcc dot gnu.org
2023-07-07 10:29 ` [Bug target/54063] [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-54063-4-m8GU6TxX2P@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).