From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: vladimir@codesourcery.com (Vladimir Prus), gdb-patches@sourceware.org
Subject: Re: [2/10] Remove &builtin_type_ from tdep code (amd64/s390/sparc64)
Date: Wed, 13 Jun 2007 13:57:00 -0000 [thread overview]
Message-ID: <200706131356.l5DDur80016141@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070613133702.GA24327@caradoc.them.org> from "Daniel Jacobowitz" at Jun 13, 2007 09:37:02 AM
Daniel Jacobowitz wrote:
> On Wed, Jun 13, 2007 at 03:17:09PM +0200, Ulrich Weigand wrote:
> > Daniel Jacobowitz wrote:
> > > On Wed, Jun 13, 2007 at 03:06:11PM +0200, Ulrich Weigand wrote:
> > > > However, this macro is not fully equivalent; in particular it
> > > > is no longer possible to use &builtin_type_double.
> > >
> > > You keep saying this, but is it true? :-)
> >
> > Well, you can take the address, but you won't get the gdbarch-swap
> > effect any more. So if you were relying on that, it'll break ...
>
> Right. Fortunately here we don't need the swap effect, since we have
> the right gdbarch - but I'd forgotten about post_init.
Also, in nearly all the cases an address of a builtin_type_ was taken,
it was in the context of a static initialization expression -- and
*there*, the macro would indeed be an error, as it no longer
represents a constant expression.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-06-13 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 23:15 Ulrich Weigand
2007-06-12 15:09 ` Daniel Jacobowitz
2007-06-12 15:57 ` Ulrich Weigand
2007-06-12 15:14 ` Daniel Jacobowitz
2007-06-12 16:07 ` Ulrich Weigand
2007-06-13 7:08 ` Vladimir Prus
2007-06-13 13:06 ` Ulrich Weigand
2007-06-13 13:09 ` Daniel Jacobowitz
2007-06-13 13:17 ` Ulrich Weigand
2007-06-13 13:36 ` Daniel Jacobowitz
2007-06-13 13:57 ` Ulrich Weigand [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=200706131356.l5DDur80016141@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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