> On 11/06/2017 12:11 AM, Uros Bizjak wrote:
> > On Mon, Nov 6, 2017 at 12:19 AM, Peryt, Sebastian
> > wrote:
> >>> On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian
> >>>
> >>> wrote:
> Hi,
>
> After r253934 gcc.target/i386/pr71321.c started to fail due to the wrong
> >>> number
On 11/06/2017 12:11 AM, Uros Bizjak wrote:
> On Mon, Nov 6, 2017 at 12:19 AM, Peryt, Sebastian
> wrote:
>>> On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian
>>>
>>> wrote:
Hi,
After r253934 gcc.target/i386/pr71321.c started to fail due to the wrong
>>> number of scan-assembler -
On Mon, Nov 6, 2017 at 12:19 AM, Peryt, Sebastian
wrote:
>> On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian
>> wrote:
>> > Hi,
>> >
>> > After r253934 gcc.target/i386/pr71321.c started to fail due to the wrong
>> number of scan-assembler - 2 instead of 3. This patch is fixing that.
>>
>> Are yo
> On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian
> wrote:
> > Hi,
> >
> > After r253934 gcc.target/i386/pr71321.c started to fail due to the wrong
> number of scan-assembler - 2 instead of 3. This patch is fixing that.
>
> Are you sure that there is no problem with the code generation? Did you
On Sun, Nov 5, 2017 at 12:14 PM, Peryt, Sebastian
wrote:
> Hi,
>
> After r253934 gcc.target/i386/pr71321.c started to fail due to the wrong
> number of scan-assembler - 2 instead of 3. This patch is fixing that.
Are you sure that there is no problem with the code generation? Did
you investigate
Hi,
After r253934 gcc.target/i386/pr71321.c started to fail due to the wrong number
of scan-assembler - 2 instead of 3. This patch is fixing that.
2017-11-05 Sebastian Peryt
PR testsuite/82767
* gcc.target/i386/pr71321.c: Fix invalid testcase.
Is it ok for trunk?
Thanks,
Sebastian
