From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ureg alignment
Date: Fri, 9 May 2014 11:52:26 -0400 [thread overview]
Message-ID: <bd4243e2ca850a6dd6980bfc1e3e7efe@ladd.quanstro.net> (raw)
In-Reply-To: <CAOw7k5iZdMyz=GuQPSMa_q4PxN7e4wLmEJOUY94Qae09_ofnaw@mail.gmail.com>
On Fri May 9 11:46:05 EDT 2014, charles.forsyth@gmail.com wrote:
> On 9 May 2014 16:29, erik quanstrom <quanstro@quanstro.net> wrote:
>
> > do you think that's perhaps worth leaving the
> > #define in as a temporary measure?
> >
>
> but if you're working with arm, the existing union is fine as it is, so why
> not just leave it?
the point is to make things like debugging arm, mips or 386 snapshots work on
amd64. without a change, cross-platform debugging doesn't work in all cases.
- erik
prev parent reply other threads:[~2014-05-09 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 14:21 erik quanstrom
2014-05-09 14:28 ` Steven Stallion
2014-05-09 14:31 ` erik quanstrom
2014-05-09 14:56 ` Charles Forsyth
2014-05-09 15:29 ` erik quanstrom
2014-05-09 15:45 ` Charles Forsyth
2014-05-09 15:52 ` erik quanstrom [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=bd4243e2ca850a6dd6980bfc1e3e7efe@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).