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 tree-optimization/28238] [4.2 regression] verify_stmts failed (invalid operand to unary operator) Date: Tue, 04 Jul 2006 13:58:00 -0000 [thread overview] Message-ID: <20060704135844.21144.qmail@sourceware.org> (raw) In-Reply-To: <bug-28238-12387@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from rguenth at gcc dot gnu dot org 2006-07-04 13:58 ------- Ah no, verify_stmts uses error (). -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|error-recovery, rejects- | |valid | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28238
next prev parent reply other threads:[~2006-07-04 13:58 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-03 22:17 [Bug tree-optimization/28238] New: " tbm at cyrius dot com 2006-07-03 22:18 ` [Bug tree-optimization/28238] " tbm at cyrius dot com 2006-07-03 22:28 ` pinskia at gcc dot gnu dot org 2006-07-03 23:16 ` pinskia at gcc dot gnu dot org 2006-07-04 13:56 ` rguenth at gcc dot gnu dot org 2006-07-04 13:58 ` rguenth at gcc dot gnu dot org [this message] 2006-07-04 14:14 ` rguenth at gcc dot gnu dot org 2006-07-06 10:55 ` [Bug tree-optimization/28238] [4.1/4.2 " rguenth at gcc dot gnu dot org 2006-07-06 12:39 ` rguenth at gcc dot gnu dot org 2006-07-06 14:55 ` pinskia at gcc dot gnu dot org 2006-07-06 14:55 ` patchapp at dberlin dot org 2006-07-17 3:03 ` mmitchel at gcc dot gnu dot org 2006-07-17 8:04 ` rguenth at gcc dot gnu dot org 2006-07-17 8:05 ` [Bug tree-optimization/28238] [4.1 " rguenth at gcc dot gnu dot org 2006-07-24 10:28 ` rguenth at gcc dot gnu dot org 2006-07-24 10:28 ` rguenth 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=20060704135844.21144.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).