On 10/03/2017 10:45 AM, Sandra Loosemore wrote:
On 10/03/2017 05:36 AM, Martin Jambor wrote:
Hi,
On Mon, Oct 02, 2017 at 01:27:05PM -0600, Sandra Loosemore wrote:
Is there an idiom for target-specific back end code to ask the pass
manager
if a particular pass (e.g., "split1") has already run?
On 10/03/2017 05:36 AM, Martin Jambor wrote:
Hi,
On Mon, Oct 02, 2017 at 01:27:05PM -0600, Sandra Loosemore wrote:
Is there an idiom for target-specific back end code to ask the pass manager
if a particular pass (e.g., "split1") has already run?
(I might be wrong but) I don't think there is.
On Tue, Oct 03, 2017 at 09:11:05AM -0600, Jeff Law wrote:
> On 10/03/2017 05:36 AM, Martin Jambor wrote:
> > Hi,
> >
> > On Mon, Oct 02, 2017 at 01:27:05PM -0600, Sandra Loosemore wrote:
> >> Is there an idiom for target-specific back end code to ask the pass manager
> >> if a particular pass (e.g
On 10/03/2017 05:36 AM, Martin Jambor wrote:
> Hi,
>
> On Mon, Oct 02, 2017 at 01:27:05PM -0600, Sandra Loosemore wrote:
>> Is there an idiom for target-specific back end code to ask the pass manager
>> if a particular pass (e.g., "split1") has already run?
>
> (I might be wrong but) I don't thin
Hi,
On Mon, Oct 02, 2017 at 01:27:05PM -0600, Sandra Loosemore wrote:
> Is there an idiom for target-specific back end code to ask the pass manager
> if a particular pass (e.g., "split1") has already run?
(I might be wrong but) I don't think there is. But it might be a
useful thing to have gener
Is there an idiom for target-specific back end code to ask the pass
manager if a particular pass (e.g., "split1") has already run?
I have some nios2 addressing mode improvement patches in the works that
depend on deferring splitting of some complex address forms until after
cse and fwprop, ins
