public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "Yuri Rumyantsev" <ysrumyan@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	"Igor Zamyatin" <izamyatin@gmail.com>,
	"Илья Энкович" <enkovich.gnu@gmail.com>
Subject: Re: [PATCH] Missing Skylake -march=/-mtune= option
Date: Wed, 19 Aug 2015 10:47:00 -0000	[thread overview]
Message-ID: <CAFiYyc1_ENBM+Z=itFgF61dV9-PbXsh0ja=v4pc3r+NpzKsgxg@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4a87MB1EOPHPP9DVNTCY1E5ZiqFupZDgmLDJ-nmpt9SLA@mail.gmail.com>

On Thu, Aug 13, 2015 at 9:57 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
> On Thu, Aug 13, 2015 at 11:31 AM, Yuri Rumyantsev <ysrumyan@gmail.com> wrote:
>> Hi All,
>>
>> Here is patch for adding march/mtune options for Skylake.
>>
>> Bootstrap and regression testing did not show any new failures.
>>
>> Is it OK for trunk?
>
> OK.

I think this causes

FAIL: g++.dg/ext/mv16.C  -std=gnu++98 execution test
FAIL: g++.dg/ext/mv16.C  -std=gnu++11 execution test
FAIL: g++.dg/ext/mv16.C  -std=gnu++14 execution test

for me.  Possibly __builtin_cpu_is is not working for skylake?

Richarad.

> Thanks,
> Uros.
>
>> ChangeLog:
>> 2015-08-13  Yuri Rumyantsev  <ysrumyan@gmail.com>
>>
>> * config/i386/driver-i386.c (host_detect_local_cpu): Add support
>> for skylake.
>> * config/i386/i386.c (PTA_SKYLAKE): New macros.
>> (processor_alias_table): Add skylake description.
>> (enum processor_model): Add skylake processor.
>> (arch_names_table): Add skylake record.
>> * doc/invoke.texi: Add skylake item.
>>
>> gcc/testsuite/ChangeLog:
>> * gcc.target/i386/builtin_target.c: Add skylake check.
>>
>> libgcc/ChangeLog:
>> * config/i386/cpuinfo.c (enum processor_subtypes): Add skylake.
>> (get_intel_cpu): Likewise.

  reply	other threads:[~2015-08-19 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  9:36 Yuri Rumyantsev
2015-08-13 20:05 ` Uros Bizjak
2015-08-19 10:47   ` Richard Biener [this message]
2015-08-19 11:11     ` Uros Bizjak
2015-08-19 11:39       ` Richard Biener
2015-08-20 15:52 ` Markus Trippelsdorf
2015-08-23 14:46   ` Markus Trippelsdorf

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='CAFiYyc1_ENBM+Z=itFgF61dV9-PbXsh0ja=v4pc3r+NpzKsgxg@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=enkovich.gnu@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=izamyatin@gmail.com \
    --cc=ubizjak@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).