From: Tom Musta <tommusta@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: "list@suse.de:PowerPC" <qemu-ppc@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [V2 PATCH 6/9] target-ppc: Load Quadword
Date: Wed, 05 Feb 2014 10:12:47 -0600 [thread overview]
Message-ID: <52F262FF.4010909@gmail.com> (raw)
In-Reply-To: <1DE1A896-D6CB-4F22-82BC-723B2EA7AA73@suse.de>
On 2/5/2014 3:43 AM, Alexander Graf wrote:
> I would've expected the compiler to emit a warning at this point because you're declaring variables outside of the beginning of a scope?
I did not see a warning on either of my test platforms (PowerPC/RHEL/GCC 4.4.7, Intel/Ubuntu/GCC 4.6.3). But I will certainly fix.
next prev parent reply other threads:[~2014-02-05 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 19:33 [Qemu-devel] [V2 PATCH 0/9] target-ppc: Base ISA V2.07 for Power8 Tom Musta
2014-01-31 19:33 ` [Qemu-devel] [V2 PATCH 1/9] target-ppc: Add Flag for bctar Tom Musta
2014-01-31 19:33 ` [Qemu-devel] [V2 PATCH 2/9] target-ppc: Add Target Address SPR (TAR) to Power8 Tom Musta
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 3/9] target-ppc: Add bctar Instruction Tom Musta
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 4/9] target-ppc: Add Flag for ISA 2.07 Load/Store Quadword Instructions Tom Musta
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 5/9] target-ppc: Add is_user_mode Utility Routine Tom Musta
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 6/9] target-ppc: Load Quadword Tom Musta
2014-02-05 9:43 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-02-05 16:12 ` Tom Musta [this message]
2014-02-05 16:27 ` Eric Blake
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 7/9] target-ppc: Store Quadword Tom Musta
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 8/9] target-ppc: Add Load Quadword and Reserve Tom Musta
2014-01-31 19:34 ` [Qemu-devel] [V2 PATCH 9/9] target-ppc: Add Store Quadword Conditional Tom Musta
2014-02-05 9:48 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-02-05 16:14 ` Tom Musta
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=52F262FF.4010909@gmail.com \
--to=tommusta@gmail.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).