Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Petr Sorfa <petrs@caldera.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] DW_AT_calling_convention support
Date: Wed, 10 Jul 2002 11:49:00 -0000	[thread overview]
Message-ID: <20020710184750.GB923@nevyn.them.org> (raw)
In-Reply-To: <npr8ibxw79.fsf@zwingli.cygnus.com>

On Wed, Jul 10, 2002 at 01:40:58PM -0500, Jim Blandy wrote:
> 
> Petr Sorfa <petrs@caldera.com> writes:
> > > Okay, I'll look forward to the patch.
> > In a few minutes.
> > 
> > > Is checking the calling convention really the approved technique for
> > > recognizing a Fortran entry point in Dwarf 2?  Is it really the case
> > > that Fortran programs always only have one function with this calling
> > > convention?  Would your patch do something sensible if it found more
> > > than one?
> > Good question, the Dwarf standard V3 Draft 7 Page 44 says:
> > 
> > "The DW_CC_program value is intended to support Fortran main programs.
> > It is not intended as
> > a way of finding the entry address for the program."
> > 
> > So the answer is yes and no. But I think the patch is valid as it
> > determines not the entry point, but the main program. As far as I am
> > aware you can have only one PROGRAM entry per FORTRAN program. If there
> > is more than one found, the patch just uses the last read entry. I don't
> > think supporting a more intricate way would be much use (such as keeping
> > a list of DW_CC_program entries.)
> 
> What's the difference between the entry point and the main program?

The entry point is an implementation detail - like _start.  The main
program is in user code, main() or "program foo".

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-07-10 18:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 14:08 Petr Sorfa
2002-07-09 14:24 ` Daniel Jacobowitz
2002-07-09 14:58   ` Petr Sorfa
2002-07-09 15:05     ` Daniel Jacobowitz
2002-07-10  7:03       ` Petr Sorfa
2002-07-10  7:19         ` Daniel Jacobowitz
2002-07-10  7:25           ` Petr Sorfa
2002-07-10  8:02             ` Daniel Jacobowitz
2002-07-10  9:07               ` Jim Blandy
2002-07-10 10:00                 ` Petr Sorfa
2002-07-10 10:18                   ` Petr Sorfa
2002-07-10 10:33                     ` Jim Blandy
2002-07-10 11:32                       ` Petr Sorfa
2002-07-10 11:47                         ` Jim Blandy
2002-07-10 11:49                           ` Daniel Jacobowitz [this message]
2002-07-10 12:35                             ` Jim Blandy
2002-07-10 12:27                           ` Daniel Berlin
2002-07-10  8:26           ` Andrew Cagney

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=20020710184750.GB923@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=petrs@caldera.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