From: "Jim Blandy" <jimb@red-bean.com>
To: "Andrew STUBBS" <andrew.stubbs@st.com>
Cc: "GDB Patches" <gdb-patches@sourceware.org>
Subject: Re: [patch][sh] mac.l insn endian issue
Date: Fri, 01 Feb 2008 22:40:00 -0000 [thread overview]
Message-ID: <8f2776cb0802011440h56d3125x4292eb803ad4771b@mail.gmail.com> (raw)
In-Reply-To: <47A2F3AF.4090009@st.com>
I don't think long long is guaranteed to be 64 bits long, but this is
certainly better than what's there now. (I gather that STMicro has a
blanket assignment.) So this looks okay to me. Should Antony add
himself to the write-after-approval list?
next prev parent reply other threads:[~2008-02-01 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 10:26 Andrew STUBBS
2008-02-01 22:40 ` Jim Blandy [this message]
2008-02-04 11:54 ` Andrew STUBBS
2008-02-04 13:40 ` Daniel Jacobowitz
2008-02-04 17:27 ` Andrew STUBBS
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=8f2776cb0802011440h56d3125x4292eb803ad4771b@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=andrew.stubbs@st.com \
--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