public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/34934] -O1 crash compile *** glibc detected *** /usr/lib/gcc/i486-linux-gnu/4.2.3/cc1: double free or corruption (!prev) Date: Thu, 24 Jan 2008 10:59:00 -0000 [thread overview] Message-ID: <20080124102656.14232.qmail@sourceware.org> (raw) In-Reply-To: <bug-34934-15677@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from rguenth at gcc dot gnu dot org 2008-01-24 10:26 ------- Confirmed. With the gcc_assert patch on x86_64 it ICEs with -O -m32 with the following reduced testcase: typedef struct fdstruct { int entry[(1024 - 10) + 2]; int last_entry; } fdlist; void vsendto_one(long*, __builtin_va_list); void sendto_realops_lev(long *umode, fdlist *l, int lev, ...) { int i, fd; __builtin_va_list vl; __builtin_va_start(vl, lev); for (fd = l->entry[i = 1]; i <= l->last_entry; fd = l->entry[++i]) { switch (lev) { case 1: if (!(*umode & 0x00000020)) continue; case 3: if (!(*umode & 0x00000080)) continue; case 9: if (!(*umode & 0x04000000)) continue; case 4: if (!(*umode & 0x00000200)) continue; case 8: if (!(*umode & 0x00100000)) continue; case 6: if (!(*umode & 0x00000100)) continue; case 7: if (!(*umode & 0x00040000)) continue; case 10: if (!(*umode & 0x00000020) && ((*umode & 0x00008000) || (*umode & 0x08000000))) continue; } vsendto_one(umode, vl); } } Obviously for a densely connected CFG there can be as much as n_basic_blocks^2 edges. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu dot | |org, rguenth at gcc dot gnu | |dot org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |ice-on-valid-code Last reconfirmed|0000-00-00 00:00:00 |2008-01-24 10:26:55 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34934
next prev parent reply other threads:[~2008-01-24 10:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-23 3:26 [Bug c/34934] New: " eshkinkot at gmail dot com 2008-01-23 4:02 ` [Bug c/34934] " eshkinkot at gmail dot com 2008-01-23 4:39 ` eshkinkot at gmail dot com 2008-01-23 8:55 ` [Bug middle-end/34934] " Ralf dot Wildenhues at gmx dot de 2008-01-23 8:55 ` Ralf dot Wildenhues at gmx dot de 2008-01-23 10:57 ` rguenth at gcc dot gnu dot org 2008-01-23 17:50 ` Ralf dot Wildenhues at gmx dot de 2008-01-23 22:22 ` rguenth at gcc dot gnu dot org 2008-01-23 22:41 ` Ralf dot Wildenhues at gmx dot de 2008-01-24 10:59 ` rguenth at gcc dot gnu dot org [this message] 2008-01-24 11:20 ` [Bug middle-end/34934] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org 2008-01-24 11:48 ` rguenth at gcc dot gnu dot org 2008-01-24 12:03 ` jakub at gcc dot gnu dot org 2008-01-24 15:42 ` jakub at gcc dot gnu dot org 2008-01-24 16:38 ` [Bug middle-end/34934] [4.1/4.2 " jakub at gcc dot gnu dot org 2008-07-04 22:30 ` [Bug middle-end/34934] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-31 15:02 ` jsm28 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=20080124102656.14232.qmail@sourceware.org \ --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).