Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jason Merrill <jason@redhat.com>
Cc: Wu Zhou <woodzltc@cn.ibm.com>,
	gcc-patches@gcc.gnu.org, 	gdb-patches@sourceware.org,
	pinskia@gcc.gnu.org
Subject: Re: [RFC] Use DW_CC_program to indicate Fortran main subroutine
Date: Mon, 21 Nov 2005 22:03:00 -0000	[thread overview]
Message-ID: <20051121163733.GA23783@nevyn.them.org> (raw)
In-Reply-To: <4381F707.5080703@redhat.com>

On Mon, Nov 21, 2005 at 11:34:15AM -0500, Jason Merrill wrote:
> Daniel Jacobowitz wrote:
> >As for calling set_main_name, I don't know if this is right or not.  I
> >guess it depends what the DWARF folks meant by "not intended as a way
> >of finding the entry address for the program".  Can a Fortran binary
> >have more than one "main program"?
> >
> >If they only meant "it does not indicate the address you can jump to in
> >order to start", then this seems quite reasonable.
> 
> This makes sense to me.  The "entry address" sounds like _start, not main.
> 
> It does seem a bit odd to put this under the calling convention 
> attribute, though, as the main function might be callable using the 
> normal calling convention in some languages.  Java, for instance.

Right - and it might not be, e.g. DW_CC_GNU_renesas_sh.  I think Dan's
got the right idea; we should just make up a tag for this, and submit
it for dwarf4.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-11-21 16:37 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 [this message]
2005-11-22  8:15       ` Wu Zhou
2006-02-20 17:22         ` Daniel Jacobowitz
2006-02-24  4:42           ` Wu Zhou

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=20051121163733.GA23783@nevyn.them.org \
    --to=drow@false.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jason@redhat.com \
    --cc=pinskia@gcc.gnu.org \
    --cc=woodzltc@cn.ibm.com \
    /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