From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbarch: ABFD no longer available at gdbarch_update_p time
Date: Thu, 13 Jun 2002 11:06:00 -0000 [thread overview]
Message-ID: <3D08DF24.9000700@cygnus.com> (raw)
In-Reply-To: <20020613175057.GA27905@nevyn.them.org>
> - global option is set
>> - architecture update is forced
>> -- architecture variant identified (using info, globals, and the last
>> architecture)
>
>
> This bit I'm a bit fuzzy on. Isn't the point that the last
> architecture might someday be CRIS - in 'set mips abi'?
It was the case - current_gdbarch could have been pointing to CRIS when
you were selecting MIPS.
Two things changed:
- current_gdbarch is now set to NULL during an architecture update (so
that can't be used)
- arches is kept sorted with most recently selected always at the front
so that arches->gdbarch is ...
> Oh, from the
> comment below it looks like you mean "the last architecture of this
> family". OK.
Yes.
> For MIPS this means that I'm going to have to carry over:
> osabi
> some ABI information which may not be available, but I could probably
> save.
>
> The latter would be the case for 'set mips abi auto', if the binary had
> been loaded under 'set mips abi o32'. We no longer know what the
> binary's ABI is but that is easy to fix.
Ah, yes, good point. The abi from the binary and the one that was selected.
Andrew
prev parent reply other threads:[~2002-06-13 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 8:14 Daniel Jacobowitz
2002-06-13 9:18 ` Andrew Cagney
2002-06-13 10:50 ` Daniel Jacobowitz
2002-06-13 11:06 ` Andrew Cagney [this message]
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=3D08DF24.9000700@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb@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