This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PR 44707 testcase failure
- From: Mike Stump <mikestump at comcast dot net>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: David Edelsohn <dje dot gcc at gmail dot com>, Jakub Jelinek <jakub at redhat dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 18 Nov 2011 09:30:12 -0800
- Subject: Re: PR 44707 testcase failure
- References: <201111181704.pAIH4IdI030037@d06av02.portsmouth.uk.ibm.com>
On Nov 18, 2011, at 9:04 AM, "Ulrich Weigand" <uweigand@de.ibm.com> wrote:
> David Edelsohn wrote:
>> I noticed that gcc.c-torture/compile/pr44707.c fails on AIX because it
>> generates invalid assembly language:
>>
>> # 12 "/farm/dje/src/src/gcc/testsuite/gcc.c-torture/compile/pr44707.c" 1
>> /* 0(6) 0(7) 0(8) 0(9) 0(10) */
>> # 0 "" 2
>>
>> I'm confused why
>>
>> __asm__ volatile ("/* %0 %1 %2 %3 %4 */" : : "nro" (e1), "nro" (e2), "nro" (e3
>>
>> is suppose to be valid on all targets when assembled.
>
> Huh, it seems the test in this form assumes the assembler supports /* ... */
> comments. But this isn't really necessary for the test to work; I think the
> best fix would be to just remove the comment and simply write
>
> __asm__ volatile ("" : : "nro" (e1), "nro" (e2), "nro" (e3 ...
>
> instead.
Sounds good to me.