On Sat, Feb 01, 2014 at 11:55:22AM +, Richard Sandiford wrote:
> Uros Bizjak writes:
> >> The scan-assembler test in vector26.C was showing up unresolved for c++98,
> >> since in that case we report an expected error and don't produce any asm.
> >>
> >> Tested on mips64-linux-gnu and applied a
Uros Bizjak writes:
>> The scan-assembler test in vector26.C was showing up unresolved for c++98,
>> since in that case we report an expected error and don't produce any asm.
>>
>> Tested on mips64-linux-gnu and applied as obvious.
>
> -// { dg-final { scan-assembler-not "globl\[ \t]*_Z3bar" } }
>
Uros Bizjak writes:
> Hello!
>
>> The scan-assembler test in vector26.C was showing up unresolved for c++98,
>> since in that case we report an expected error and don't produce any asm.
>>
>> Tested on mips64-linux-gnu and applied as obvious.
>
> -// { dg-final { scan-assembler-not "globl\[ \t]*_
Hello!
> The scan-assembler test in vector26.C was showing up unresolved for c++98,
> since in that case we report an expected error and don't produce any asm.
>
> Tested on mips64-linux-gnu and applied as obvious.
-// { dg-final { scan-assembler-not "globl\[ \t]*_Z3bar" } }
+// { dg-final { scan
The scan-assembler test in vector26.C was showing up unresolved for c++98,
since in that case we report an expected error and don't produce any asm.
Tested on mips64-linux-gnu and applied as obvious.
Thanks,
Richard
gcc/testsuite/
* g++.dg/ext/vector26.C: Restrict scan-assembler test to
