This is the mail archive of the
mailing list for the GCC project.
Re: pass manager question
- From: Jeff Law <law at redhat dot com>
- To: Sandra Loosemore <sandra at codesourcery dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 3 Oct 2017 09:11:05 -0600
- Subject: Re: pass manager question
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=law at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com EE31EC04AC6E
- References: <59D29309.firstname.lastname@example.org> <email@example.com>
On 10/03/2017 05:36 AM, Martin Jambor wrote:
> 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 generally, it would allow us for example to merge
> early SRA and "late" SRA which differ in behavior only because the
> first one must not touch aggregates that pass_stdarg will operate on.
I was thinking that it would be useful to be able to make this kind of
query as well.
> And I guess the infrastructure to do that could be as simple as adding
> a flag (or a counter) to class opt_pass that the pass manager would
> set (or increment) when running the pass.
And as a cleanup that flag ought to be able to replace some of the
existing state flags. I'm thinking about reload_in_progress,
reload_completed, cse_not_expected and likely others.