On Thu, Sep 3, 2015 at 1:02 PM, Jeff Law wrote:
> Agreed. I think the google project went further, but with Lawrence retiring,
> I think it's been abandoned.
We got up to the point where we could store and re-use pre-parsed
images of headers. The big problem were those headers with exposed
re
On 09/08/2015 12:05 PM, Abe wrote:
Dear all,
In order to be able to implement this idea for stores, I think I need
to make some changes to the RTL if-converter such that it will
sometimes add -- to the code being compiled -- a new slot/variable in
the stack frame. This memory needs to be addres
IIUC, in the haifa-sched.c, the default scheduling algorithm seems to be
top-down (before reload).
Is there a way to schedule the other way (bottom up), or both ways?
As a use case for bottom-up or some other heuristic:
Currently, the first priority in the selection is given to the longest path,
On Tue, Sep 08, 2015 at 06:39:19PM +, Aditya K wrote:
> IIUC, in the haifa-sched.c, the default scheduling algorithm seems to be
> top-down (before reload).
> Is there a way to schedule the other way (bottom up), or both ways?
>
> As a use case for bottom-up or some other heuristic:
> Current
On 09/08/2015 12:39 PM, Aditya K wrote:
IIUC, in the haifa-sched.c, the default scheduling algorithm seems to
be top-down (before reload). Is there a way to schedule the other way
(bottom up), or both ways?
Not that I'm aware of. Note that region scheduling allows insns to move
between basic bl
On 09/07/2015 10:05 AM, Konstantin Vladimirov wrote:
Hi,
In private backend for GCC 5.2.0, we do have target-specific scheduler
(running in TARGET_SCHED_FINISH hook), that do some instruction
packing/pairing on sched2 and relies on REG_DEAD notes, that should be
correct.
But they aren't because
> Subject: Re: Combined top-down and bottom-up instruction scheduler
> To: hiradi...@msn.com; gcc@gcc.gnu.org
> CC: vmaka...@redhat.com
> From: l...@redhat.com
> Date: Tue, 8 Sep 2015 12:51:24 -0600
>
> On 09/08/2015 12:39 PM, Aditya K wrote:
>> IIUC, in t
Segher Boessenkool wrote:
> On Tue, Sep 08, 2015 at 06:39:19PM +, Aditya K wrote:
> > IIUC, in the haifa-sched.c, the default scheduling algorithm seems to be
> > top-down (before reload).
> > Is there a way to schedule the other way (bottom up), or both ways?
> >
> > As a use case for bottom
On 09/08/2015 02:51 PM, Jeff Law wrote:
On 09/08/2015 12:39 PM, Aditya K wrote:
IIUC, in the haifa-sched.c, the default scheduling algorithm seems to
be top-down (before reload). Is there a way to schedule the other way
(bottom up), or both ways?
Not that I'm aware of. Note that region scheduli
On 09/08/2015 01:40 PM, Vladimir Makarov wrote:
As I remember it is was written by Mike Tiemann.
Correct.
Bottom-up scheduler as
a rule generates worse code than top-down one.
Indeed that was one of the key things we were looking to get from the
Haifa scheduler along with improved supers
On 09/08/2015 01:24 PM, Aditya K wrote:
Subject: Re: Combined top-down and bottom-up instruction scheduler
To: hiradi...@msn.com; gcc@gcc.gnu.org
CC: vmaka...@redhat.com
From: l...@redhat.com
Date: Tue, 8 Sep 2015 12:51:24 -0600
On 09/08/2015 12:39 PM,
> > Yes, that is true for OOO execution processors which can rearrange
> > insns and execute them speculatively looking through several branches.
> > For such processors, software pipelining is more important as the
> > processors can look only through a few branches as software pipelining
> > coul
On 09/08/2015 03:12 PM, Evandro Menezes wrote:
cache miss and transcendental functions). You might also attack
secondary
issues like throughput at the retirement stage for example.
Our motivation stems from the fact that even modern, aggressively OOO
processors don't have orthogonal resourc
Snapshot gcc-5-20150908 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150908/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
[David, we're talking about moving the GCC repository to Git, and how to
handle subdirectory branches.]
On 09/04/2015 12:17 PM, Joseph Myers wrote:
branches/st is more complicated than simply being a container for
subdirectory branches. It has a README file, five cli* subdirectories
that look
15 matches
Mail list logo
