This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] gcc::context creation
- From: Nathan Sidwell <nathan at acm dot org>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Richard Biener <richard dot guenther at gmail dot com>, Martin Liška <mliska at suse dot cz>
- Date: Wed, 24 May 2017 07:44:49 -0400
- Subject: Re: [PATCH] gcc::context creation
- Authentication-results: sourceware.org; auth=none
- References: <7f7f64a5-f820-a19a-d4ea-77b05f746499@acm.org> <98b0273e-9390-18ce-c041-31f843b8b1f8@acm.org> <20170524105728.GZ8499@tucnak>
On 05/24/2017 06:57 AM, Jakub Jelinek wrote:
So, first question, where should we order the -fdump-lang-* dumps, shall
they go before .original/.gimple/.nested, or in between .original and
.gimple/.nested, or after those 3 (the last option looks just wrong to me)?
I think the lang dumps should come first.
Shall the 3 standard dumps be registered like any others?
I think they should move to the new dynamic registration.
Should 'original' become a lang dump?
Shall the number of lang dumps affect the numbering, i.e. is it desirable
that with C and C++ you get different numbers for *t.cfg dump, or *t.gimple?
In many cases it would be better if the numbering was consistent between C
and C++.
I'm ambivalent on this. I can see why consistency might be desirable
though. I'd be fine with making the lang dumps unnumbered to achieve
that -- I don't see an obvious need for a language to have two dumps of
the same name.
nathan
--
Nathan Sidwell