public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/48614] New: gcc.target/i386/pr46084.c should require avx_runtime
Date: Fri, 15 Apr 2011 00:03:00 -0000 [thread overview]
Message-ID: <bug-48614-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48614
Summary: gcc.target/i386/pr46084.c should require avx_runtime
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: zsojka@seznam.cz
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Currently, that test fails with -ftree-vectorize in RUNTESTFLAGS:
$ gcc gcc.target/i386/pr46084.c -fsplit-stack -O2 -mavx -ftree-vectorize
$ gdb ./a.out
Program received signal SIGILL, Illegal instruction.
0x0000000000400d0e in use_buffer (buf=Unhandled dwarf expression opcode 0xf3
) at gcc.target/i386/pr46084.c:21
21 for (i = 0; i < c; ++i)
(gdb) disassemble
Dump of assembler code for function use_buffer:
...
0x0000000000400d02 <+98>: lea 0x1(%rax),%rdx
0x0000000000400d06 <+102>: mov %rax,-0x10(%rsp)
0x0000000000400d0b <+107>: add %rdi,%rcx
=> 0x0000000000400d0e <+110>: vmovq -0x10(%rsp),%xmm0
0x0000000000400d14 <+116>: vpinsrq $0x1,%rdx,%xmm0,%xmm1
0x0000000000400d1a <+122>: vmovdqa 0x10ae(%rip),%xmm13 # 0x401dd0
0x0000000000400d22 <+130>: xor %edx,%edx
0x0000000000400d24 <+132>: vmovdqa 0x10b4(%rip),%xmm0 # 0x401de0
0x0000000000400d2c <+140>: vmovdqa 0x10bc(%rip),%xmm9 # 0x401df0
0x0000000000400d34 <+148>: vmovdqa 0x10c4(%rip),%xmm8 # 0x401e00
0x0000000000400d3c <+156>: vmovdqa 0x10cc(%rip),%xmm12 # 0x401e10
0x0000000000400d44 <+164>: vmovdqa 0x10d4(%rip),%xmm11 # 0x401e20
0x0000000000400d4c <+172>: jmp 0x400d54 <use_buffer+180>
I know I am using custom RUNTESTFLAGS, but if the fix is as easy as adding "{
dg-require-effective-target avx_runtime }", it would be nice to have it fixed.
Index: gcc/testsuite/gcc.target/i386/pr46084.c
===================================================================
--- gcc/testsuite/gcc.target/i386/pr46084.c (revision 172439)
+++ gcc/testsuite/gcc.target/i386/pr46084.c (working copy)
@@ -2,6 +2,7 @@
only run on Unix. */
/* { dg-do run { target *-*-linux* *-*-solaris* *-*-darwin* } } */
/* { dg-require-effective-target avx } */
+/* { dg-require-effective-target avx_runtime } */
/* { dg-require-effective-target split_stack } */
/* { dg-options "-fsplit-stack -O2 -mavx" } */
Prevents the failure, but I am not sure if the line above the change isn't now
redundant.
next reply other threads:[~2011-04-15 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 0:03 zsojka at seznam dot cz [this message]
2011-04-15 10:29 ` [Bug testsuite/48614] " jakub at gcc dot gnu.org
2011-04-15 10:30 ` jakub at gcc dot gnu.org
2011-04-15 10:35 ` jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-48614-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).