public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>,    libc-ports@sourceware.org
Subject: Re: [PATCH roland/arm-unified] ARM: Convert string/ assembly to unified syntax.
Date: Mon, 11 Mar 2013 21:25:00 -0000	[thread overview]
Message-ID: <20130311212512.004662C08D@topped-with-meat.com> (raw)
In-Reply-To: Carlos O'Donell's message of  Monday, 11 March 2013 17:19:26 -0400 <513E4A5E.6020404@redhat.com>

> When you verified the assembled instructions were unchanged did
> you look to see that the opcodes were the same or that disassembling
> the result yielded the same previously disassembled instructions?

Both: I compared the output of objdump -rd and there were no differences at
all.  That compared both the disassembly and the hex bytes.

  reply	other threads:[~2013-03-11 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 18:22 Roland McGrath
2013-03-11 21:19 ` Carlos O'Donell
2013-03-11 21:25   ` Roland McGrath [this message]
2013-03-11 23:35 ` Joseph S. Myers

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=20130311212512.004662C08D@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).