public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Yuri Rumyantsev <ysrumyan@gmail.com>,
	       Richard Biener <richard.guenther@gmail.com>,
	       gcc-patches <gcc-patches@gcc.gnu.org>,
	       Igor Zamyatin <izamyatin@gmail.com>
Subject: Re: [PATCH PR69652, Regression]
Date: Mon, 29 Feb 2016 13:05:00 -0000	[thread overview]
Message-ID: <20160229130520.GY3017@tucnak.redhat.com> (raw)
In-Reply-To: <CAMe9rOoyfbKZTiN=NnvANsFLjq33iMhZ2EiKZbn6HcNNkMqxwg@mail.gmail.com>

On Mon, Feb 29, 2016 at 05:01:52AM -0800, H.J. Lu wrote:
> On Mon, Feb 29, 2016 at 3:53 AM, Yuri Rumyantsev <ysrumyan@gmail.com> wrote:
> > This test simply checks that ICE is not occurred but not any
> > vectorization issues.
> 
> Can we remove
> 
>  /* { dg-options "-O2 -ffast-math -ftree-vectorize " } */
> 
> then?

Well, I bet -ffast-math -ftree-vectorize are needed to reproduce the ICE
with broken compiler.  But, e.g. -O0 -ftree-vectorize doesn't make much
sense to test.
So, either put it into gcc.dg/pr69652.c with the above mentioned options,
or into gcc.dg/vect/ with dg-additional-options "-ffast-math".

	Jakub

  reply	other threads:[~2016-02-29 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 14:46 Yuri Rumyantsev
2016-02-04 16:40 ` Jakub Jelinek
2016-02-05 14:54   ` Yuri Rumyantsev
2016-02-09 12:33     ` Richard Biener
2016-02-10 10:26       ` Yuri Rumyantsev
2016-02-10 13:25         ` Richard Biener
2016-02-28 17:29         ` H.J. Lu
2016-02-29 11:53           ` Yuri Rumyantsev
2016-02-29 13:01             ` H.J. Lu
2016-02-29 13:05               ` Jakub Jelinek [this message]
2016-02-29 14:03                 ` Yuri Rumyantsev
2016-02-29 14:06                   ` Jakub Jelinek

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=20160229130520.GY3017@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=izamyatin@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=ysrumyan@gmail.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).