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/32218] New: [4.2/4.3 Regression] segfault with -O1 -ftree-vectorize Date: Tue, 05 Jun 2007 08:31:00 -0000 [thread overview] Message-ID: <bug-32218-12387@http.gcc.gnu.org/bugzilla/> (raw) I'm getting the following segfault on IA-64 with current 4.2 and 4.3. This goes back at least to 20060721 - I don't have anything older to test here at the moment. I don't see this segfault on x86_64. Unfortunately I don't have a working gdb on ia-64 at the moment so I cannot supply a backtrace. tbm@coconut0:~$ /usr/lib/gcc-snapshot/bin/gcc -c -O1 -ftree-vectorize /home/tbm/poc-streamer-ogg-write.c /home/tbm/poc-streamer-ogg-write.c: In function 'ogg_fill_page_hdr': /home/tbm/poc-streamer-ogg-write.c:14: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. Testcase: typedef struct buf_s { unsigned long size; } buf_t; typedef struct ogg_page_s { unsigned char page_segments; unsigned char lacing_values[255]; buf_t raw; } ogg_page_t; ogg_fill_page_hdr (ogg_page_t *page) { unsigned long size = page->page_segments; int i; for (i = 0; i < page->page_segments; i++) size += page->lacing_values[i]; if (page->raw.size < size) for (i = 0; i < page->page_segments; i++) continue; } -- Summary: [4.2/4.3 Regression] segfault with -O1 -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=32218
next reply other threads:[~2007-06-05 8:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-05 8:31 tbm at cyrius dot com [this message] 2007-06-06 23:44 ` [Bug target/32218] " sje at cup dot hp dot com 2007-06-30 9:15 ` pinskia at gcc dot gnu dot org 2007-07-01 11:23 ` dorit at gcc dot gnu dot org 2007-07-01 11:32 ` tbm at cyrius dot com 2007-07-01 11:33 ` tbm at cyrius dot com 2007-07-03 20:19 ` sje at cup dot hp dot com 2007-07-04 3:24 ` mmitchel at gcc dot gnu dot org 2007-07-20 3:52 ` mmitchel at gcc dot gnu dot org 2007-07-24 8:53 ` dorit at gcc dot gnu dot org 2007-07-24 18:37 ` tbm at cyrius dot com 2007-07-25 16:20 ` sje at cup dot hp dot com 2007-07-25 20:24 ` sje at gcc dot gnu dot org 2007-07-26 16:30 ` sje at cup dot hp dot com 2007-07-26 16:38 ` pluto at agmk dot net 2007-07-26 16:44 ` sje at cup dot hp dot com 2007-07-30 15:16 ` sje 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-32218-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).