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 REV 2
Date: Thu, 11 Jul 2002 08:07:00 -0000	[thread overview]
Message-ID: <3D2D9FB1.87EABC20@caldera.com> (raw)
In-Reply-To: <20020710193458.GA28939@nevyn.them.org>

Hi Daniel,

> main_name(), I assume.  Basically I would like everywhere that
> currently checks by a strcmp/STREQ with main_name() to use
> is_main_symbol () instead, etc.  Things that call lookup_symbol on
> main_name() should just use get_main_symbol () if possible.  Then
> set_main_name () could include calling lookup_symbol(main_name()), so
> that get_main_symbol would always be valid, etc....
Unforuntately after looking at this I realized this will not work always
correctly. It is quite possible that a symbol is not created for "main"
until much later. There are calls to set_main_name() before the symbol
is created, so your proposition to do a lookup_symbol() in
set_main_name() will not work in all cases.

I suggest that the get_main_symbol() is altered to your suggestions, to
which I want to add further checks such as ensuring that the main name
is equal to the main symbol's name.

If this is ok with you, I'll do a rev 3 patch for this and submit it.

Petr


  parent reply	other threads:[~2002-07-11 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 11:41 Petr Sorfa
2002-07-10 11:47 ` Daniel Jacobowitz
2002-07-10 12:32   ` Petr Sorfa
2002-07-10 12:41     ` Daniel Jacobowitz
2002-07-10 14:06       ` Petr Sorfa
2002-07-11  8:07       ` Petr Sorfa [this message]
2002-07-11  9:22         ` Daniel Jacobowitz

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=3D2D9FB1.87EABC20@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