public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: Joern Rennecke <joernr@arc.com>
Cc: cgen@sources.redhat.com
Subject: Re: subword semantics
Date: Fri, 19 Jan 2007 15:30:00 -0000	[thread overview]
Message-ID: <45B0E3FA.2090801@redhat.com> (raw)
In-Reply-To: <20070119120733.GA2043@elsdt-razorfish.arc.com>

Joern Rennecke wrote:

>What are the actual semantics of subword?
>The documentation says that it is endian dependent, but the existing
>bi-endian ports always use word 0 to refer to the most significant part.
>  
>
You are correct. The semantics are not endian dependent. Similar to the 
way shift operators are not endian dependent. The documentation also 
says that dependence on endianness was to be revisited. Perhaps that's 
what happend, or perhaps the intent was to recommend caution when using 
a (mem ...) expression as the operand of (subword ...)

Dave

      reply	other threads:[~2007-01-19 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 12:07 Joern Rennecke
2007-01-19 15:30 ` Dave Brolley [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=45B0E3FA.2090801@redhat.com \
    --to=brolley@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=joernr@arc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).