From: Jim Blandy <jimb@redhat.com>
To: Petr Sorfa <petrs@caldera.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
"gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] DW_AT_calling_convention support
Date: Wed, 10 Jul 2002 10:33:00 -0000 [thread overview]
Message-ID: <npwus3xzr6.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3D2C6B1B.B9DA55FC@caldera.com>
Petr Sorfa <petrs@caldera.com> writes:
> Ok, during testing I realized that I have to detect DW_AT_calling before
> symbol creation while reading in dies and types (I had this in the
> original patch, but removed it thinking it was redundant.) The main
> reason is to call set_main_name() so that the correct program language
> is determined on program load before execution. set_main_symbol() is now
> called within new_symbol().
Okay, I'll look forward to the patch.
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?
next prev parent reply other threads:[~2002-07-10 17:24 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 [this message]
2002-07-10 11:32 ` Petr Sorfa
2002-07-10 11:47 ` Jim Blandy
2002-07-10 11:49 ` Daniel Jacobowitz
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=npwus3xzr6.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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