This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/11243] New: [3.4 regression] segfault on valid code initializing a vector
- From: "kazu at cs dot umass dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Jun 2003 20:36:43 -0000
- Subject: [Bug c/11243] New: [3.4 regression] segfault on valid code initializing a vector
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11243
Summary: [3.4 regression] segfault on valid code initializing a
vector
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: kazu@cs.umass.edu
CC: gcc-bugs@gcc.gnu.org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
void
foo ()
{
__attribute__((vector_size(16))) int a = {123, 456};
}
segfaults on 3.4 as of June 18, 2003. This piece of code compiles fine on 3.3
branch, meaning this is a regression. You don't need any options. "./cc1
foo.c" is enough to cause a segfault.