public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/32230] New: [4.3 Regression] Segfault in set_bb_for_stmt with -O -ftree-vectorize Date: Wed, 06 Jun 2007 07:52:00 -0000 [thread overview] Message-ID: <bug-32230-12387@http.gcc.gnu.org/bugzilla/> (raw) I'm getting the following segfault on trunk with -O -ftree-vectorize. This was introduced between 20070422 and 20070515. (sid)25522:tbm@em64t: ~] /usr/lib/gcc-snapshot/bin/gcc -O -ftree-vectorize -c glame-waveform.c glame-waveform.c: In function 'const_f': glame-waveform.c:18: warning: comparison of distinct pointer types lacks a cast glame-waveform.c:12: internal compiler error: Segmentation fault Please submit a full bug report, [...] (sid)25523:tbm@em64t: ~] /usr/lib/gcc-snapshot/bin/gcc -ftree-vectorize -c glame-waveform.c glame-waveform.c: In function 'const_f': glame-waveform.c:18: warning: comparison of distinct pointer types lacks a cast (sid)25524:tbm@em64t: ~] Testcase: typedef struct filter_buffer filter_buffer_t; struct filter_buffer { char buf[1]; }; typedef struct sbuf_header sbuf_header_t; struct sbuf_header { char buf[1]; } const_f (filter_buffer_t *buf) { float val; int i; for (i = 0; i < 10; i++) ((float *) (&((sbuf_header_t *) ((buf) == &(buf)->buf[0]))->buf[0]))[i] = val; } -- Summary: [4.3 Regression] Segfault in set_bb_for_stmt with -O - ftree-vectorize Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tbm at cyrius dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32230
next reply other threads:[~2007-06-06 7:52 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-06 7:52 tbm at cyrius dot com [this message] 2007-06-06 7:53 ` [Bug tree-optimization/32230] " tbm at cyrius dot com 2007-06-06 20:47 ` pinskia at gcc dot gnu dot org 2007-06-06 20:52 ` pinskia at gcc dot gnu dot org 2007-06-06 20:53 ` pinskia at gcc dot gnu dot org 2007-06-26 12:19 ` eres at il dot ibm dot com 2007-06-28 9:02 ` irar at il dot ibm dot com 2007-06-28 11:41 ` irar at il dot ibm dot com 2007-06-28 12:20 ` rguenther at suse dot de 2007-06-28 12:29 ` irar at il dot ibm dot com 2007-06-28 12:30 ` rguenther at suse dot de 2007-06-28 12:38 ` irar at il dot ibm dot com 2007-06-29 18:39 ` mmitchel at gcc dot gnu dot org 2007-07-01 11:15 ` patchapp at dberlin dot org 2007-07-02 10:27 ` irar at gcc dot gnu dot org 2007-07-02 19:41 ` pinskia at gcc dot gnu dot 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-32230-12387@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: linkBe 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).