public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsturm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/13733] [tree-ssa] internal compiler error: in check_pointer_types_r, at gimplify.c:3460
Date: Mon, 19 Jan 2004 05:45:00 -0000 [thread overview]
Message-ID: <20040119054554.19687.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040119014759.13733.jsturm@gcc.gnu.org>
------- Additional Comments From jsturm at gcc dot gnu dot org 2004-01-19 05:45 -------
(In reply to comment #2)
> The java front-end is not converting the trees to gimple right.
That's not precisely correct since java isn't responsible for conversion to
gimple, aside from a few minor langhooks. Either the generic trees produced are
wrong or the gimplifier is misbehaving somewhere.
After compiling the statement
if ((result = this.member).binding == arg)
to generic, the nested MODIFY_EXPR has type (DerivedBug *). The gimplifier
reduces the above to:
struct DerivedBug * T.1;
struct java.lang.Object * T.2;
struct Bug * result;
T.1 = this->member;
result = T.1;
T.2 = result->binding; <---
if (T.2 == arg)
note that the INDIRECT_REF now has "result" as its operand. This operand
substitution is legal provided the operands have the same type, but they do not.
IMO the INDIRECT_REF should have been gimplified into
T.2 = T.1->binding;
with no need for type conversion, since T.1 is equivalent to the result of the
original MODIFY_EXPR.
--
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|tree-ssa |---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13733
next prev parent reply other threads:[~2004-01-19 5:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 1:48 [Bug java/13733] New: " jsturm at gcc dot gnu dot org
2004-01-19 1:49 ` [Bug java/13733] " jsturm at gcc dot gnu dot org
2004-01-19 1:57 ` jsturm at gcc dot gnu dot org
2004-01-19 3:38 ` pinskia at gcc dot gnu dot org
2004-01-19 3:41 ` [Bug java/13733] [tree-ssa] " pinskia at gcc dot gnu dot org
2004-01-19 5:45 ` jsturm at gcc dot gnu dot org [this message]
2004-01-20 3:48 ` pinskia at gcc dot gnu dot org
2004-01-21 1:03 ` jsturm at gcc dot gnu dot org
2004-01-21 2:31 ` [Bug java/13733] The result of an assignment operator is the LHS after assignment, not the RHS giovannibajo at libero dot it
2004-01-22 23:45 ` cvs-commit at gcc dot gnu dot org
2004-01-23 0:21 ` cvs-commit at gcc dot gnu dot org
2004-01-23 1:41 ` jsturm at gcc dot gnu dot org
2004-01-23 1:43 ` pinskia at gcc dot gnu dot org
2004-01-23 1:45 ` pinskia 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=20040119054554.19687.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).