From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jason Merrill <jason@redhat.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
pinskia@gcc.gnu.org, dberlin@dberlin.org,
jimb@red-bean.com
Subject: Re: [RFC] Use DW_CC_program to indicate Fortran main subroutine
Date: Fri, 24 Feb 2006 04:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0602232128320.6966@localhost.localdomain> (raw)
In-Reply-To: <20060220172244.GC19356@nevyn.them.org>
On Mon, 20 Feb 2006, Daniel Jacobowitz wrote:
> On Tue, Nov 22, 2005 at 10:34:01AM +0800, Wu Zhou wrote:
> > Hi,
> >
> > Thank you all for your kind input. I had a look at all your comments. It
> > seems that no one is 100% convinced that DW_CC_program is the proper
> > solution. In fact I am also a little odd about the usage of DW_CC_program
> > to indicate the main function. But the text in DWARF 3.3.1 really induce
> > me to think that it is currently the only feasible solution.
> >
> > Now that most of you concur to make up a new attribute or tag for this. I
> > think it is more correct too. Maybe it is time for us to discuss the
> > detail of this new tag or attribute?
> >
> > My vote is to use a new attribute Dan Berlin proposed: DW_AT_GNU_main. We
> > can use it in GNU toolchain first, gcc, gdb, binutils and so on. If the
> > DWARF committee can reach agreement on the final name, we can switch to
> > it then. What is your point on this? Thanks.
>
> Since we had this conversation DWARF-3 was published; did you want to
> reopen this with the DWARF working group?
Yes. Good point. It is time to do that. But I am not sure how to
re-open the deferred issue with the DWARF group. I just sent out a mail
to ask how. Hopefully someone can reply quickly.
BTW. Anyone have any comments about using DW_AT_GNU_main first in GNU
tools? I still like this idea. We don't need to wait for DWARF group's
decision, which might be long.
Regards
- Wu Zhou
prev parent reply other threads:[~2006-02-24 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 7:28 Wu Zhou
2005-11-21 14:14 ` Daniel Jacobowitz
2005-11-21 14:58 ` Jim Blandy
2005-11-21 16:37 ` Daniel Berlin
2005-11-21 18:10 ` Daniel Berlin
2005-11-21 22:02 ` Jason Merrill
2005-11-21 22:03 ` Daniel Jacobowitz
2005-11-22 8:15 ` Wu Zhou
2006-02-20 17:22 ` Daniel Jacobowitz
2006-02-24 4:42 ` Wu Zhou [this message]
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.0602232128320.6966@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=dberlin@dberlin.org \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jason@redhat.com \
--cc=jimb@red-bean.com \
--cc=pinskia@gcc.gnu.org \
/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