From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: riscv-tdep.c in 32-bits build
Date: Fri, 21 Dec 2018 15:22:00 -0000 [thread overview]
Message-ID: <87va3msy4t.fsf@tromey.com> (raw)
In-Reply-To: <20181221005727.GF3456@embecosm.com> (Andrew Burgess's message of "Fri, 21 Dec 2018 00:57:27 +0000")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> Anyway, I propose casting to LONGEST and printing that. Unless you
Andrew> object I'll push this in a few days.
It's fine; but as CORE_ADDR is (and will always be) unsigned, I think
you could use pulongest without a cast.
Tom
prev parent reply other threads:[~2018-12-21 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 17:26 Simon Marchi
2018-12-21 0:57 ` Andrew Burgess
2018-12-21 15:22 ` Tom Tromey [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=87va3msy4t.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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