From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [2/10] Remove &builtin_type_ from tdep code (amd64/s390/sparc64)
Date: Wed, 13 Jun 2007 13:09:00 -0000 [thread overview]
Message-ID: <20070613131002.GA23051@caradoc.them.org> (raw)
In-Reply-To: <200706131306.l5DD6BO8021072@d12av02.megacenter.de.ibm.com>
On Wed, Jun 13, 2007 at 03:06:11PM +0200, Ulrich Weigand wrote:
> To that purpose, the builtin_type_double global variable will
> go away, and is (temporarily) replaced by a macro
>
> #define builtin_type_double
> builtin_type (current_gdbarch)->builtin_double
>
> 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? :-)
You can't take the address of a function's return value, but you can
take the address of a dereference. Of course using
&builtin_type_double in m68k_gdbarch_init won't work since
current_gdbarch is NULL then. But we should be able to save
builtin_type (gdbarch)->builtin_double if we wanted to, I think.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-13 13:09 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 [this message]
2007-06-13 13:17 ` Ulrich Weigand
2007-06-13 13:36 ` Daniel Jacobowitz
2007-06-13 13:57 ` Ulrich Weigand
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=20070613131002.GA23051@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
--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