Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Petr Sorfa <petrs@caldera.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] DW_AT_calling_convention support
Date: Wed, 10 Jul 2002 07:25:00 -0000	[thread overview]
Message-ID: <3D2C4567.3AD10A8B@caldera.com> (raw)
In-Reply-To: <20020710140354.GA25081@nevyn.them.org>

Hi Daniel,

Great, however I do suggest get_main_symbol() for greater flexibility.
I've moved the code to deal with DW_AT_calling_convention into
dwarf2read.c's new_symbol() function (as opposed to detecting it while
reading a type). Let me know what you think and I'll have a patch ready
soon.

Petr
> On Wed, Jul 10, 2002 at 09:53:35AM -0400, Petr Sorfa wrote:
> > Hi Daniel,
> >
> > > I'd rather save a pointer the symbol for the main function, or
> > > something along those lines - do you think that's workable?
> > Sounds good. Note that I'm making the assumption that the symbol is
> > associated with a type that is only associated with that symbol (iff).
> >
> > I think it should be API driven, like set_main_symbol () and
> > get_main_symbol () and situated in symtab.c alonside set_main_name() and
> > main_name().
> 
> Yep, that's about what I had in mind.  How about:
> 
>   set_main_name ()
>   set_main_symbol ()
>   is_main_symbol ()
>     - if a main symbol is set, check if it is the same symbol
>     - otherwise, check if it has the same name as passed to
>       set_main_name
> 
> (with appropriate care for when we change object files.... to one
> without a DWARF-2 main symbol, even...)
> 
> --
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-07-10 14:19 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 [this message]
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
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=3D2C4567.3AD10A8B@caldera.com \
    --to=petrs@caldera.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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