qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Liang Li <liang.z.li@intel.com>, Amit Shah <amit.shah@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] AVX2 configure fixes
Date: Mon, 13 Jun 2016 11:58:55 +0100	[thread overview]
Message-ID: <20160613105854.GB2281@work-vm> (raw)
In-Reply-To: <CAFEAcA-1a=pV7mjcym7X3HfHcDqK5+To=46TdMy5qqQYicci2A@mail.gmail.com>

* Peter Maydell (peter.maydell@linaro.org) wrote:
> On 10 June 2016 at 12:16, Dr. David Alan Gilbert (git)
> <dgilbert@redhat.com> wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Hi,
> >   This pair of patches fixes a couple of issues that we found during test.
> > The first is that the configure test is pessimistic when compiled with -O2,
> > the second is that the explicit 4.9 gcc test is a bit coarse; I've removed
> > that test but beefed up the ./configure test to actually use the avx2
> > intrinsics and that fails in the same way as the main code, so it works
> > in the same way as the explicit check but allows older gcc's to work
> > when -save-temps isn't used.
> >
> > Dave
> >
> > v3
> >   Use compile_object rather than compile_prog as suggested by Peter to
> >   hopefully fail on his ccache setup.
> 
> I ran these patches through my build tests and it all compiled OK,
> so the new configure test does correctly say "no AVX" on this setup.

Thanks for checking.

Dave

> 
> thanks
> -- PMM
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      reply	other threads:[~2016-06-13 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 11:16 [Qemu-devel] [PATCH v3 0/2] AVX2 configure fixes Dr. David Alan Gilbert (git)
2016-06-10 11:16 ` [Qemu-devel] [PATCH v3 1/2] Make avx2 configure test work with -O2 Dr. David Alan Gilbert (git)
2016-06-10 11:16 ` [Qemu-devel] [PATCH v3 2/2] avx2 configure: Use primitives in test Dr. David Alan Gilbert (git)
2016-07-14 13:13   ` Aaron Lindsay
2016-07-14 13:15     ` Paolo Bonzini
2016-07-14 13:23       ` Peter Maydell
2016-07-14 14:27         ` Aaron Lindsay
2016-07-14 14:35           ` Peter Maydell
2016-07-14 19:44             ` Aaron Lindsay
2016-07-14 13:33     ` Dr. David Alan Gilbert
2016-07-14 14:18       ` Aaron Lindsay
2016-07-14 15:05         ` Dr. David Alan Gilbert
2016-07-14 19:36           ` Aaron Lindsay
2016-07-14 19:38             ` [Qemu-devel] [PATCH] avx2 configure: Disable if static build Aaron Lindsay
2016-07-19 19:12               ` Dr. David Alan Gilbert
2016-07-29 14:22                 ` Peter Maydell
2016-06-13  9:31 ` [Qemu-devel] [PATCH v3 0/2] AVX2 configure fixes Paolo Bonzini
2016-06-13 10:51 ` Peter Maydell
2016-06-13 10:58   ` Dr. David Alan Gilbert [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=20160613105854.GB2281@work-vm \
    --to=dgilbert@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=liang.z.li@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 NNTP newsgroup(s).