Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: David Edelsohn <dje@watson.ibm.com>,
	Elena Zannoni <ezannoni@cygnus.com>,
	Zack Weinberg <zackw@Stanford.EDU>,
	Matthew Conway <matt_conway@i2.com>,
	Mark Mitchell <mark@codesourcery.com>,
	gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Limited success with 3.0 branch on AIX
Date: Wed, 16 May 2001 14:06:00 -0000	[thread overview]
Message-ID: <3B02EB6E.F4F74251@apple.com> (raw)
In-Reply-To: <1010516205027.ZM11789@ocotillo.lan>

Kevin Buettner wrote:
> 
>     /* Version of GCC used to compile the function corresponding
>        to this block, or 0 if not compiled with GCC.  When possible,
>        GCC should be compatible with the native compiler, or if that
>        is not feasible, the differences should be fixed during symbol
>        reading.  As of 16 Apr 93, this flag is never used to distinguish
>        between gcc2 and the native compiler.

(page page page...) My creaky and failing memory recalls configs
where GCC did not produce code that was 100% compatible with the
vendor compiler, for instance in the area of struct returns.  So GDB
needed to know which convention was in use, and in the absence of
better hints (such as when -g wasn't specified), the gcc2_compiled
symbol would get the info through.  (It matters for the non-debug
case because we may need to walk through non-debug frames to get to
the frames of interest.)

I think it's still possible to use GCC in a way that makes the
label necessary, for instance by using some of the more dubious
flags in some of the more obscure configs, but I doubt that PowerPC
is one of them.  I'd suggest blasting this old stuff anyway, adding
a cautionary note to the internals manual ("don't let the compiler
do this, ever" and reopening the issue afresh should it come up again.

Stan


  reply	other threads:[~2001-05-16 14:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15106.54023.177141.275660@kwikemart.cygnus.com>
2001-05-16 12:37 ` David Edelsohn
2001-05-16 13:07 ` David Edelsohn
2001-05-16 13:51   ` Kevin Buettner
2001-05-16 14:06     ` Stan Shebs [this message]
2001-05-16 14:10       ` David Edelsohn
2001-05-16 14:32     ` Elena Zannoni
2001-05-16 21:29   ` Elena Zannoni
2001-05-17 15:27     ` David Edelsohn
     [not found] <200104302116.RAA23290@makai.watson.ibm.com>
2001-05-02 23:25 ` Zack Weinberg
2001-05-03  1:42   ` Kevin Buettner
2001-05-15 15:27     ` Elena Zannoni
2001-05-15 15:31       ` David Edelsohn
2001-05-15 16:19         ` Elena Zannoni
2001-05-16 10:46           ` David Edelsohn
2001-05-16 11:15           ` David Edelsohn
2001-05-16 12:24             ` Elena Zannoni
     [not found] <OF70310855.A41D4A39-ON86256A39.00616113@i2.com>
2001-05-01 10:13 ` David Edelsohn
2001-05-01 13:02   ` Daniel Berlin
2001-05-01 13:22     ` David Edelsohn
2001-05-01 15:40       ` Kevin Buettner
2001-05-01 15:44         ` David Edelsohn
2001-05-01 16:21   ` Kevin Buettner
2001-05-01 19:15     ` David Edelsohn

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=3B02EB6E.F4F74251@apple.com \
    --to=shebs@apple.com \
    --cc=dje@watson.ibm.com \
    --cc=ezannoni@cygnus.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@cygnus.com \
    --cc=mark@codesourcery.com \
    --cc=matt_conway@i2.com \
    --cc=zackw@Stanford.EDU \
    /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