On Tue, Oct 6, 2015 at 9:09 AM, Kirill Yukhin wrote:
> Hello Uroš,
>
> I've merged two patches together and rebased it
> on top of gcc-5-branch. The only change I made compared
> to trunk version is scheduling set to CPU_NEHALEM since
> CPU_HASWELL is not supported in gcc-5.
>
> Bootstrapped.
>
>
One more missed hunk:
iff --git a/gcc/testsuite/gcc.target/i386/builtin_target.c
b/gcc/testsuite/gcc.target/i386/builtin_target.c
index 9eb397e..cbca6b4 100644
--- a/gcc/testsuite/gcc.target/i386/builtin_target.c
+++ b/gcc/testsuite/gcc.target/i386/builtin_target.c
@@ -173,6 +173,10 @@ check_feat
Hello Uroš,
I've merged two patches together and rebased it
on top of gcc-5-branch. The only change I made compared
to trunk version is scheduling set to CPU_NEHALEM since
CPU_HASWELL is not supported in gcc-5.
Bootstrapped.
Is it ok for gcc-5-branch?
gcc/
* config.gcc: Support "skylake
On Fri, Oct 2, 2015 at 6:12 PM, Kirill Yukhin wrote:
> Hello,
>
> Patch in the bottom introduces cpuid detection
> for Skylake CPU supporting AVX-512.
>
> Bootstrapped. Changed test pass. Is it ok for trunk?
>
> libgcc/
> * libgcc/config/i386/cpuinfo.c (get_intel_cpu): Detect
> "skylake-a
Hello,
Patch in the bottom introduces cpuid detection
for Skylake CPU supporting AVX-512.
Bootstrapped. Changed test pass. Is it ok for trunk?
libgcc/
* libgcc/config/i386/cpuinfo.c (get_intel_cpu): Detect "skylake-avx512".
gcc/testsuite/
* gcc.target/i386/builtin_target.c: Add
On Tue, Sep 22, 2015 at 11:31 AM, Kirill Yukhin wrote:
> Hello Uroš,
> On 21 Sep 19:19, Uros Bizjak wrote:
>> On Mon, Sep 21, 2015 at 6:57 PM, Kirill Yukhin
>> wrote:
>> > Patch in the bottom. Is it ok?
>>
>> Comments inline.
>>
>> > -native"
>> > +native skylake-avx512"
>>
>> Please leave x86-6
Hello Uroš,
On 21 Sep 19:19, Uros Bizjak wrote:
> On Mon, Sep 21, 2015 at 6:57 PM, Kirill Yukhin
> wrote:
> > Patch in the bottom. Is it ok?
>
> Comments inline.
>
> > -native"
> > +native skylake-avx512"
>
> Please leave x86-64 and native at the last two places. They are generic
> entries.
D
On Mon, Sep 21, 2015 at 6:57 PM, Kirill Yukhin wrote:
> Hi Uroš, Jakub,
> eOn 21 Sep 16:27, Jakub Jelinek wrote:
>> On Mon, Sep 21, 2015 at 05:14:45PM +0300, Kirill Yukhin wrote:
>> > Hello,
>> > This patch introduces switches necessary for new Intel Server CPU
>> > (code-named Skylake).
>> >
>> >
Hello HJ,
On 21 Sep 07:40, H.J. Lu wrote:
> On Mon, Sep 21, 2015 at 7:14 AM, Kirill Yukhin
> wrote:
> > Hello,
> > This patch introduces switches necessary for new Intel Server CPU
> > (code-named Skylake).
> >
> > Bootstrapped & regtested.
> >
> > Is it ok for trunk?
> > gcc/testsuite/
> >
Hi Uroš, Jakub,
eOn 21 Sep 16:27, Jakub Jelinek wrote:
> On Mon, Sep 21, 2015 at 05:14:45PM +0300, Kirill Yukhin wrote:
> > Hello,
> > This patch introduces switches necessary for new Intel Server CPU
> > (code-named Skylake).
> >
> > Bootstrapped & regtested.
> Is it a good idea to introduce furt
On Mon, Sep 21, 2015 at 4:27 PM, Jakub Jelinek wrote:
> On Mon, Sep 21, 2015 at 05:14:45PM +0300, Kirill Yukhin wrote:
>> Hello,
>> This patch introduces switches necessary for new Intel Server CPU
>> (code-named Skylake).
>>
>> Bootstrapped & regtested.
>>
>> Is it ok for trunk?
>>
>> gcc/
>>
On Mon, Sep 21, 2015 at 7:14 AM, Kirill Yukhin wrote:
> Hello,
> This patch introduces switches necessary for new Intel Server CPU
> (code-named Skylake).
>
> Bootstrapped & regtested.
>
> Is it ok for trunk?
>
> gcc/
> * config.gcc: Support "skx".
> * config/i386/i386-c.c (ix86_ta
On Mon, Sep 21, 2015 at 05:14:45PM +0300, Kirill Yukhin wrote:
> Hello,
> This patch introduces switches necessary for new Intel Server CPU
> (code-named Skylake).
>
> Bootstrapped & regtested.
>
> Is it ok for trunk?
>
> gcc/
> * config.gcc: Support "skx".
> * config/i386/i386-c.c
Hello,
This patch introduces switches necessary for new Intel Server CPU
(code-named Skylake).
Bootstrapped & regtested.
Is it ok for trunk?
gcc/
* config.gcc: Support "skx".
* config/i386/i386-c.c (ix86_target_macros_internal): Handle
PROCESSOR_SKX.
* config/i386
14 matches
Mail list logo
