linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Paul Mackerras <paulus@samba.org>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org, amodra@gmail.com
Subject: Re: [PATCH] powerpc: Use 32 bit loads and stores when operating on condition register values
Date: Tue, 15 Oct 2013 14:55:43 +1100	[thread overview]
Message-ID: <20131015145543.736684c3@kryten> (raw)
In-Reply-To: <20131015034206.GB17233@drongo>


Hi Paul,

> Does this make any practical difference or fix any bugs, or is this
> just for aesthetics?

There is talk of the other 32 bits of that word being used for a
stack canary in a future ABI revision. So right now it is just
cosmetic, but it could be important in the future.

I guess it could be an issue for kgdb since the CR will be in
the wrong spot on BE.

Anton

      reply	other threads:[~2013-10-15  3:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15  3:36 [PATCH] powerpc: Use 32 bit loads and stores when operating on condition register values Anton Blanchard
2013-10-15  3:42 ` Paul Mackerras
2013-10-15  3:55   ` Anton Blanchard [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=20131015145543.736684c3@kryten \
    --to=anton@samba.org \
    --cc=amodra@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=paulus@samba.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 NNTP newsgroup(s).