public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57836] large constants evaluated inline
Date: Thu, 15 May 2014 00:14:00 -0000	[thread overview]
Message-ID: <bug-57836-4-HHqKKzwCOI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57836-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57836

--- Comment #2 from David Edelsohn <dje at gcc dot gnu.org> ---
The affect of deligitimize_address on storing constants in the TOC vs
materializing inline was unintentional, but my JIT experiments on POWER7 did
not show a bad performance affect from materializing inline. Before we restore
the old behavior, we should try to figure out which method actually produces
better performance on recent hardware for PPC64 Linux and AIX.


  parent reply	other threads:[~2014-05-15  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-06 11:58 [Bug target/57836] New: " amodra at gmail dot com
2013-11-09 22:25 ` [Bug target/57836] " pinskia at gcc dot gnu.org
2014-05-12  6:38 ` amodra at gmail dot com
2014-05-15  0:14 ` dje at gcc dot gnu.org [this message]
2015-04-22 11:59 ` jakub at gcc dot gnu.org
2015-07-16  9:16 ` rguenth at gcc dot gnu.org
2020-04-01 23:17 ` amodra at gmail dot com

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-57836-4-HHqKKzwCOI@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).