From: Elena Zannoni <ezannoni@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: [buildsym.c] Turn off unused addr bits in linetable
Date: Sun, 01 Apr 2001 17:37:00 -0000 [thread overview]
Message-ID: <15047.51630.461134.422903@kwikemart.cygnus.com> (raw)
In-Reply-To: <3AB1733B.FEC3833E@cygnus.com>
Fernando, did you check this in? Thanks for investigating.
BTW. Sh doesn't define ADDR_BITS_REMOVE. But it uses it! I'll have to
fix that.
Elena
Andrew Cagney writes:
> Fernando Nasser wrote:
> >
> > Andrew,
> >
> > I looked at all the targets that define ADDR_BITS_REMOVE() (which are
> > arm, h8500, m88k, mips, pa, w65, z8k and sh) and all that define
> > BREAKPOINT_FROM_PC() (which are arm, mips, mcore and mn10300, as far as
> > I can tell).
> >
> > I am convinced that this is the right thing to do. I really wonder, in
> > some cases, how could it have worked without it (maybe the stub or the
> > OS cleared the bits for us).
>
> I suspect that it is like the 32 bit MIPS - no one was sure how it
> should work. Only when the decision that the 32 bit MIPS was have all
> addresses converted to cannonical form (i.e. sign extend them) did a
> heap of problems get flushed.
>
> I'd lace your patch with comments explaining how the table contains
> cannonical addresses and those addresses don't contain any stray magic
> bits. That way the next person will know where the error is when they
> find a comparison is doing strange things because the addresses don't
> quite match.
>
> > Anyway, there is only one way of knowing it for sure. The only thing we
> > know right now is that ARM is broken without it.
> >
> > OK to commit?
>
> I withdraw my objection. I think the maintainer had already approved
> it.
>
> Thanks for investigating this!
>
> Andrew
>
> PS: A multi-arch footnote (Hi nick :-): At some stage or another, an
> additional interface into BFD is going to be needed so that GDB can ask
> BFD what the architecture/machine tupple for a given address is.
> Details are for much later. This is just a little flag :-)
>
next prev parent reply other threads:[~2001-04-01 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 17:01 Fernando Nasser
2001-03-12 17:11 ` Michael Snyder
2001-03-13 8:52 ` Andrew Cagney
2001-03-13 9:21 ` Fernando Nasser
2001-03-15 16:27 ` Fernando Nasser
2001-03-15 17:58 ` Andrew Cagney
2001-04-01 17:37 ` Elena Zannoni [this message]
2001-04-06 6:23 ` Fernando Nasser
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=15047.51630.461134.422903@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=fnasser@redhat.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