public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Wei Xiao <wei.william.xiao@gmail.com>,
	       "Lu, Hongjiu" <hongjiu.lu@intel.com>,
	"H. J. Lu" <hjl.tools@gmail.com>,
	       kretz@kde.org, "Guo, Xuepeng" <xuepeng.guo@intel.com>,
	       "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] x86: Revert patches to fix PR target/88794
Date: Tue, 15 Jan 2019 15:20:00 -0000	[thread overview]
Message-ID: <20190115152050.GP30353@tucnak> (raw)
In-Reply-To: <CAFULd4bPwAVCAmWKXFt1m6GZcFxt+BAAF8V1sUZeEnPFbDku7w@mail.gmail.com>

On Tue, Jan 15, 2019 at 04:14:06PM +0100, Uros Bizjak wrote:
> On Tue, Jan 15, 2019 at 3:40 PM Wei Xiao <wei.william.xiao@gmail.com> wrote:
> >
> > Hi,
> >
> > It turns out that the Intel 64 and IA-32 Architectures Software Developer
> > Manuals (SDM) description about the fixupimm intrinsic is incorrect. So we need
> > to revert 3 patches related to it: r265827, r266026 and r267160.
> > Sorry for the inconvenience.
> >
> > Is it ok?
> 
> Yes, but please test the compiler after the revert. Please also create
> a runtime testcase out of the testcase in the PR.

For r267160, I'd expect you want to revert just the config/i386/ part and
keep the testcases, they should work even with the changes reverted, right?

	Jakub

  reply	other threads:[~2019-01-15 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 14:40 Wei Xiao
2019-01-15 15:14 ` Uros Bizjak
2019-01-15 15:20   ` Jakub Jelinek [this message]
2019-01-16 11:13     ` Wei Xiao
2019-01-16 14:48       ` Wei Xiao
2019-01-16 15:03         ` Jakub Jelinek
2019-01-17 13:03       ` [PATCH] Read avx512vl-vfixupimms*-2.c testcases (PR target/88489) Jakub Jelinek
2019-01-18  2:42         ` Wei Xiao
2019-01-18  7:55           ` Uros Bizjak

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=20190115152050.GP30353@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=hongjiu.lu@intel.com \
    --cc=kretz@kde.org \
    --cc=ubizjak@gmail.com \
    --cc=wei.william.xiao@gmail.com \
    --cc=xuepeng.guo@intel.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).