public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/14682] [tree-ssa] error: Invalid operand to binary operator Date: Thu, 01 Apr 2004 18:40:00 -0000 [thread overview] Message-ID: <20040401184019.12813.qmail@sources.redhat.com> (raw) In-Reply-To: <20040322193838.14682.aj@gcc.gnu.org> ------- Additional Comments From law at redhat dot com 2004-04-01 18:40 ------- Subject: Re: [tree-ssa] error: Invalid operand to binary operator In message <20040401182528.GB30425@redhat.com>, Richard Henderson writes: >On Thu, Apr 01, 2004 at 10:32:08AM -0700, law@redhat.com wrote: >> + /* Note that the folders should only create gimple expressions. >> + This is a hack until the new folder is ready. */ >> + in_gimple_form = 1; >> + >> /* Perform all tree transforms and optimizations. */ >> execute_pass_list (all_passes); >> + >> + /* Note that the folders can create non-gimple expressions again. */ >> + in_gimple_form = 1; > >Typo second time. Thanks. Brain fart. I also changed them to use true/false respectively. jeff -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14682
next prev parent reply other threads:[~2004-04-01 18:40 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-22 19:38 [Bug c/14682] New: " aj at gcc dot gnu dot org 2004-03-22 19:39 ` [Bug c/14682] " aj at gcc dot gnu dot org 2004-03-22 19:53 ` [Bug middle-end/14682] [tree-ssa] " pinskia at gcc dot gnu dot org 2004-03-22 20:13 ` [Bug c/14682] " falk at debian dot org 2004-03-22 20:16 ` [Bug middle-end/14682] " pinskia at gcc dot gnu dot org 2004-03-22 20:20 ` [Bug optimization/14682] " pinskia at gcc dot gnu dot org 2004-03-22 21:14 ` steven at gcc dot gnu dot org 2004-03-22 21:17 ` pinskia at gcc dot gnu dot org 2004-03-22 21:27 ` steven at gcc dot gnu dot org 2004-03-22 21:34 ` steven at gcc dot gnu dot org 2004-03-22 22:11 ` pinskia at gcc dot gnu dot org 2004-03-22 22:43 ` law at redhat dot com 2004-03-23 2:53 ` pinskia at gcc dot gnu dot org 2004-03-23 2:58 ` pinskia at gcc dot gnu dot org 2004-03-23 14:28 ` law at redhat dot com 2004-03-26 21:58 ` dje at gcc dot gnu dot org 2004-03-27 12:31 ` steven at gcc dot gnu dot org 2004-03-28 0:54 ` dnovillo at gcc dot gnu dot org 2004-04-01 17:32 ` law at redhat dot com 2004-04-01 17:40 ` law at gcc dot gnu dot org 2004-04-01 18:24 ` rth at redhat dot com 2004-04-01 18:25 ` rth at redhat dot com 2004-04-01 18:40 ` law at redhat dot com [this message] 2004-04-01 18:42 ` dnovillo at redhat dot com 2004-04-01 19:01 ` law at redhat dot com
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=20040401184019.12813.qmail@sources.redhat.com \ --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).