Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
		  Waldek Hebisch <hebisch@math.uni.wroc.pl>,
		  Pierre Muller <muller@ics.u-strasbg.fr>,
	 gdb-patches@sourceware.org, 	  gpc@gnu.de
Subject: Re: [RFC] Handle GPC specific name for main function
Date: Thu, 27 Sep 2007 19:50:00 -0000	[thread overview]
Message-ID: <m3hclflwgk.fsf@codesourcery.com> (raw)
In-Reply-To: <1190913417.25072.10.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Thu, 27 Sep 2007 14:16:57 -0300")


Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> On Wed, 2007-09-26 at 22:52 -0700, Joel Brobecker wrote:
>> It looks like we're reaching the same conclusion as before, which is
>> that, unless GPC gets changed to emit a specific symbol to specify
>> that the main is in pascal, the strongest approach is to rely on
>> DWARF data. 
>> 
>> http://www.cygwin.com/ml/gdb-patches/2005-11/msg00380.html
>
> Unfortunately, from the discussion above there is no adequate DWARF tag
> to specify which is the main program. Like Dan Berlin suggested, it is
> necessary to come up with a new one and make the compilers (gpc and
> gfortran) emit those.

The DWARF committee discussed adding a tag to do this, but it got
bogged down in questions about what to do in cases like Java and Ada
and COBOL, and how to phrase the definition to mean the right thing in
all those cases.  If the DWARF web site is up to date, the proposal
got sent back for revision.

http://dwarfstd.org/ShowIssue.php?issue=070619.1&type=open


      reply	other threads:[~2007-09-27 19:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 14:40 Pierre Muller
2007-09-26 15:03 ` Eli Zaretskii
2007-09-26 15:32   ` Pierre Muller
2007-09-26 17:48     ` Eli Zaretskii
2007-09-26 17:58 ` Joel Brobecker
2007-09-26 19:39   ` Pierre Muller
2007-09-26 19:50     ` Joel Brobecker
2007-09-26 22:06       ` Pierre Muller
2007-09-26 22:39         ` [RFC-2] " Pierre Muller
2007-09-27  6:03           ` Joel Brobecker
2007-09-27  7:29             ` [RFC-3] " Pierre Muller
     [not found]               ` <46FB5E2C.6080606@microbizz.nl>
     [not found]                 ` <46FB5F76.9050501@microbizz.nl>
2007-09-27  7:57                   ` Pierre Muller
2007-09-27 12:11                     ` Daniel Jacobowitz
2007-09-27 12:35                       ` Pierre Muller
2007-09-27 12:40                         ` 'Daniel Jacobowitz'
2007-09-27 16:20                           ` Joel Brobecker
2007-09-27 16:32                             ` Joel Brobecker
2007-09-27 21:36                               ` Pierre Muller
2007-09-28 18:31                                 ` Joel Brobecker
2007-09-27  8:02                 ` Pierre Muller
2007-09-27 13:01                   ` Waldek Hebisch
2007-09-27  7:20           ` [RFC-2] " Eli Zaretskii
2007-09-27  1:58 ` [RFC] " Waldek Hebisch
2007-09-27  5:52   ` Joel Brobecker
2007-09-27 17:17     ` Thiago Jung Bauermann
2007-09-27 19:50       ` Jim Blandy [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=m3hclflwgk.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gpc@gnu.de \
    --cc=hebisch@math.uni.wroc.pl \
    --cc=muller@ics.u-strasbg.fr \
    /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