From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA][1/5] New port: Cell BE SPU (dwarf2loc.c fix)
Date: Wed, 22 Nov 2006 02:30:00 -0000 [thread overview]
Message-ID: <20061122023019.GA14488@nevyn.them.org> (raw)
In-Reply-To: <m31wnwtfx2.fsf@codesourcery.com>
On Tue, Nov 21, 2006 at 05:43:05PM -0800, Jim Blandy wrote:
> It seems a shame to be creating a value and then throwing it away, but
> the composition of those two functions has the semantics we want, so I
> don't see a good alternative without some more restructuring.
Actually, I think we should be doing it more often. It doesn't live
long, there's a clearly defined mechanism for throwing it away, and it
encapsulates that the object should have target semantics. Eventually,
if we ever get around to disallowing math on CORE_ADDR, I think this is
what we'll end up with.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-22 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 18:37 Ulrich Weigand
2006-11-13 19:40 ` Jim Blandy
2006-11-15 21:57 ` Ulrich Weigand
2006-11-22 1:42 ` Jim Blandy
2006-11-22 2:30 ` Daniel Jacobowitz [this message]
2006-11-22 14:10 ` 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=20061122023019.GA14488@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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