public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "graphitem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51955] New: _mm_setzero_si128 intri causes segfault without -O
Date: Mon, 23 Jan 2012 01:57:00 -0000 [thread overview]
Message-ID: <bug-51955-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51955
Bug #: 51955
Summary: _mm_setzero_si128 intri causes segfault without -O
Classification: Unclassified
Product: gcc
Version: 4.6.2
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: graphitem@gmail.com
Created attachment 26419
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26419
gcc -v -save-temps output
There seems to be an issue in respect to the _mm_setzero_si128() intrinsic in
<emmintrin.h>
using the following __m128i xmm0 = _mm_setzero_si128(); causes a segmentation
fault. GDB reports the following
Program received signal SIGSEGV, Segmentation fault.
0x0000000000400631 in _mm_setzero_si128 () at
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/include/emmintrin.h:734
734 return __extension__ (__m128i)(__v4si){ 0, 0, 0, 0 };
The bug seems to dissapear when optimization levels 1,2,3 are used.
The compiler flags I'm using:
-Wall -nostdlib -std=c99 -fno-builtin -ffreestanding -pedantic-errors
GCC version and specs are below:
gcc -v:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/src/gcc-4.6-20111223/configure --prefix=/usr
--libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object
--enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto
--enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold
--enable-multilib --disable-libssp --disable-libstdcxx-pch
--enable-checking=release --with-fpmath=sse
Thread model: posix
gcc version 4.6.2 20111223 (prerelease) (GCC)
uname -a:
Linux (graphitemaster) 3.1.9-2-ARCH #1 SMP PREEMPT Sat Jan 14 09:11:37 CET 2012
x86_64 AMD Phenom(tm) AuthenticAMD GNU/Linux
attached is the gcc -v -save-temps output
next reply other threads:[~2012-01-23 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 1:57 graphitem at gmail dot com [this message]
2012-01-23 2:44 ` [Bug c/51955] _mm_setzero_si128 intrinsic " graphitem at gmail dot com
2012-01-23 2:54 ` graphitem at gmail dot com
2012-01-23 3:18 ` [Bug target/51955] " pinskia at gcc dot gnu.org
2012-01-23 7:24 ` graphitem at gmail dot com
2012-01-23 10:54 ` rguenth 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-51955-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).