public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com>,
	       Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc@gcc.gnu.org
Subject: Re: input address reload issue
Date: Fri, 06 Jan 2017 16:09:00 -0000	[thread overview]
Message-ID: <c6dd93a0-7dd5-698c-808d-c3f7367b9982@redhat.com> (raw)
In-Reply-To: <e8814ead-9c4a-8001-dfdd-83ced14ccf31@gmail.com>

On 01/06/2017 03:26 AM, Aurelien Buhrig wrote:
>
>> Look at the dump file for reload to see where things come from.  Also
>> everything Jeff said; you really want LRA.
>
> I will try switching to LRA in a second step, but I think I need first to remove the old cc0...
> BTW, in which way the LRA is better than IRA? Is there any benchmarks?
I would suggesting moving away from cc0 first.  cc0 is an abomination 
and should have been abolished years ago -- the only reason is many old 
ports would break and nobody's taken the time to convert them or propose 
them for deprecation.

While we try to keep the cc0-target paths working, they're not exercised 
all that much and can easily break.

jeff

  parent reply	other threads:[~2017-01-06 16:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 16:20 Aurelien Buhrig
2017-01-05 17:46 ` Jeff Law
2017-01-06 10:21   ` Aurelien Buhrig
2017-01-06 16:06     ` Jeff Law
2017-01-09 14:03       ` Aurelien Buhrig
2017-01-09 18:35         ` Jeff Law
2017-01-12 11:01           ` Aurelien Buhrig
2017-01-06  8:50 ` Segher Boessenkool
2017-01-06 10:28   ` Aurelien Buhrig
2017-01-06 10:53     ` Segher Boessenkool
2017-01-06 16:09     ` Jeff Law [this message]
2017-01-06 16:37       ` Eric Botcazou
2017-01-06 16:46         ` Jeff Law

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=c6dd93a0-7dd5-698c-808d-c3f7367b9982@redhat.com \
    --to=law@redhat.com \
    --cc=aurelien.buhrig.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).