public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/14682] [tree-ssa] error: Invalid operand to binary operator
Date: Mon, 22 Mar 2004 21:27:00 -0000 [thread overview]
Message-ID: <20040322212757.8131.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040322193838.14682.aj@gcc.gnu.org>
------- Additional Comments From steven at gcc dot gnu dot org 2004-03-22 21:27 -------
Perhaps. I looked in GDB:
/* Const/copy propagate into USES, VUSES and the RHS of VDEFs. */
may_have_exposed_new_symbols = cprop_into_stmt (stmt, const_and_copies);
==> Here we have:
"if (9223372036854775807 < iov_len_6) goto <L1>; else goto <L2>;"
which is good.
/* If the statement has been modified with constant replacements,
fold its RHS before checking for redundant computations. */
if (ann->modified)
{
/* Try to fold the statement making sure that STMT is kept
up to date. */
if (fold_stmt (bsi_stmt_ptr (si)))
{
==> and here we have:
"if ((long long int)iov_len_6 < 0) goto <L1>; else goto <L2>;"
which is wrong.
So fold_stmt is producing something we're not ready for.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14682
next prev parent reply other threads:[~2004-03-22 21:27 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 [this message]
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
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=20040322212757.8131.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: link
Be 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).