On Sat, Aug 20, 2016 at 1:25 AM, Patrick Palka wrote:
> On Fri, 19 Aug 2016, Yuri Rumyantsev wrote:
>
>> Hi,
>>
>> Here is a simple test-case to reproduce 176.gcc failure (I run it on
>> Haswell machine).
>> Using 20160819 compiler build we get:
>> gcc -O3 -m32 -mavx2 test.c
On Sun, Aug 21, 2016 at 11:04 PM, Patrick Palka wrote:
> On Sat, 20 Aug 2016, Uros Bizjak wrote:
>
>> > Turning it into a compile test that counts the number of jumps threaded
>> > seems potentially flaky but I'm not against it. And I'm not sure how to
>> > reliably turn it
On Sat, 20 Aug 2016, Uros Bizjak wrote:
> > Turning it into a compile test that counts the number of jumps threaded
> > seems potentially flaky but I'm not against it. And I'm not sure how to
> > reliably turn it into an execution test. Would the directives
> >
> > /* { dg-do run } */
> > /* {
> Turning it into a compile test that counts the number of jumps threaded
> seems potentially flaky but I'm not against it. And I'm not sure how to
> reliably turn it into an execution test. Would the directives
>
> /* { dg-do run } */
> /* { dg-require-effective-target avx2 } */
> /* {
On Fri, 19 Aug 2016, David Malcolm wrote:
> On Fri, 2016-08-19 at 19:25 -0400, Patrick Palka wrote:
> > On Fri, 19 Aug 2016, Yuri Rumyantsev wrote:
> >
> > > Hi,
> > >
> > > Here is a simple test-case to reproduce 176.gcc failure (I run it
> > > on
> > > Haswell machine).
> > > Using 20160819
On Fri, 2016-08-19 at 19:25 -0400, Patrick Palka wrote:
> On Fri, 19 Aug 2016, Yuri Rumyantsev wrote:
>
> > Hi,
> >
> > Here is a simple test-case to reproduce 176.gcc failure (I run it
> > on
> > Haswell machine).
> > Using 20160819 compiler build we get:
> > gcc -O3 -m32 -mavx2 test.c -o
On Fri, 19 Aug 2016, Yuri Rumyantsev wrote:
> Hi,
>
> Here is a simple test-case to reproduce 176.gcc failure (I run it on
> Haswell machine).
> Using 20160819 compiler build we get:
> gcc -O3 -m32 -mavx2 test.c -o test.ref.exe
> /users/ysrumyan/isse_6866$ ./test.ref.exe
> Aborted (core dumped)
Hi,
Here is a simple test-case to reproduce 176.gcc failure (I run it on
Haswell machine).
Using 20160819 compiler build we get:
gcc -O3 -m32 -mavx2 test.c -o test.ref.exe
/users/ysrumyan/isse_6866$ ./test.ref.exe
Aborted (core dumped)
If I apply patch proposed by Patrick test runs properly
On Fri, Aug 19, 2016 at 1:06 AM, Patrick Palka wrote:
> On Thu, 18 Aug 2016, Richard Biener wrote:
>
>> On August 18, 2016 8:25:18 PM GMT+02:00, Patrick Palka
>> wrote:
>> >In comment #5 Yuri reports that r235653 introduces a runtime failure
>> >for
On Thu, 18 Aug 2016, Richard Biener wrote:
> On August 18, 2016 8:25:18 PM GMT+02:00, Patrick Palka
> wrote:
> >In comment #5 Yuri reports that r235653 introduces a runtime failure
> >for
> >176.gcc which I guess is caused by the combining step in
>
On 08/18/2016 01:22 PM, Richard Biener wrote:
On August 18, 2016 8:25:18 PM GMT+02:00, Patrick Palka
wrote:
In comment #5 Yuri reports that r235653 introduces a runtime failure
for
176.gcc which I guess is caused by the combining step in
On August 18, 2016 8:25:18 PM GMT+02:00, Patrick Palka
wrote:
>In comment #5 Yuri reports that r235653 introduces a runtime failure
>for
>176.gcc which I guess is caused by the combining step in
>simplify_control_stmt_condition_1() not behaving properly on operands
>of
In comment #5 Yuri reports that r235653 introduces a runtime failure for
176.gcc which I guess is caused by the combining step in
simplify_control_stmt_condition_1() not behaving properly on operands of
type VECTOR_TYPE. I'm a bit stumped as to why it mishandles
VECTOR_TYPEs because the logic
13 matches
Mail list logo