From: Richard Guenther <rguenther@suse.de>
To: Tristan Gingold <gingold@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Eric Botcazou <ebotcazou@adacore.com>, Jan Hubicka <jh@suse.de>
Subject: Re: [Patch/cfgexpand]: also consider assembler_name to call expand_main_function
Date: Wed, 21 Mar 2012 07:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1203210843320.6741@jbgna.fhfr.qr> (raw)
In-Reply-To: <1D9E2C16-3989-438E-8016-837DC2E7021C@adacore.com>
On Tue, 20 Mar 2012, Tristan Gingold wrote:
>
> On Mar 20, 2012, at 5:01 PM, Richard Guenther wrote:
>
> > On Tue, 20 Mar 2012, Tristan Gingold wrote:
> >
> >>
> >> On Mar 20, 2012, at 3:19 PM, Richard Guenther wrote:
> >>
> >> [...]
> >>>
> >>> I'd rather get away from using a global main_identifier_node, instead
> >>> make that frontend specific, and introduce targetm.main_assembler_name
> >>> which the assembler-name creating langhook would make sure to use
> >>> when mangling what the FE thinks main is. main_identifier_node should
> >>> not serve any purpose outside of Frontends.
> >>>
> >>> But I see both as a possible cleanup opportunity, not a necessary change.
> >>
> >> Something along these lines ?
> >
> > Yes, but I'd simply call the hook at the places you now use
> > main_assembler_name and not create a global tree node for it.
>
> But we use it at the beginning of graph_finalize_function, so caching it
> makes sense, doesn't it ?
Well, maybe ;) I have no strong opinion here.
Richard.
next prev parent reply other threads:[~2012-03-21 7:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 16:04 Tristan Gingold
2012-03-14 16:09 ` Richard Guenther
2012-03-14 16:25 ` Tristan Gingold
2012-03-15 9:38 ` Richard Guenther
2012-03-15 12:51 ` Tristan Gingold
2012-03-20 12:07 ` Tristan Gingold
2012-03-20 12:22 ` Richard Guenther
2012-03-20 14:12 ` Tristan Gingold
2012-03-20 14:20 ` Richard Guenther
2012-03-20 16:00 ` Tristan Gingold
2012-03-20 16:02 ` Richard Guenther
2012-03-20 16:06 ` Tristan Gingold
2012-03-21 7:44 ` Richard Guenther [this message]
2012-03-20 17:18 ` Jan Hubicka
2012-03-21 8:40 ` Tristan Gingold
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=Pine.LNX.4.64.1203210843320.6741@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=jh@suse.de \
/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).