From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Swap out current when creating a new architecture
Date: Wed, 26 Sep 2001 23:06:00 -0000 [thread overview]
Message-ID: <3BB2C1E7.1080300@cygnus.com> (raw)
In-Reply-To: <1010927055546.ZM3074@ocotillo.lan>
> I'm wondering though if it might be possible to set current_gdbarch
> to the architecture currently getting defined. This way, it would
> be possible to do things like:
>
> gdbarch->target_long_bit = 8;
> gdbarch->target_long_long_bit = 2*TARGET_LONG_BIT;
>
Another option other is to rename the local variable ``gdbarch'' to
``current_gdbarch''. Check my other patch to gdbarch_alloc() which was
forced to do just that.
Personally, though, I'd prefer to be doing none of the above. Instead
just eliminate that global current_gdbarch and parameterize everthing
.... :-)
enjoy,
Andrew
next prev parent reply other threads:[~2001-09-26 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BB16441.30805@cygnus.com>
2001-09-26 22:56 ` Kevin Buettner
2001-09-26 23:06 ` Andrew Cagney [this message]
2001-09-30 12:25 ` Andrew Cagney
2001-10-01 4:34 ` Orjan Friberg
2001-10-14 17:07 ` Andrew Cagney
2001-10-15 18:41 ` Andrew Cagney
2001-10-16 1:59 ` Orjan Friberg
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=3BB2C1E7.1080300@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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