From: Steve Teale <steve.teale@britseyeview.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: gimplify.c - missing tree codes
Date: Fri, 05 Mar 2010 19:38:00 -0000 [thread overview]
Message-ID: <1267817886.20422.4.camel@Ubuntu> (raw)
In 4.3.4,the switch in function gimplify_expr(...) included:
case STATIC_CHAIN_EXPR:
/* The argument is used as information only. No need to
gimplify */
case STATIC_CHAIN_DECL:
ret = GS_ALL_DONE;
break;
4.4.3 does not mention these codes, so any front end that generates them
fails at a later catch-all with an Internal compiler error.
What was the rationale for removing them? Is it a big deal to put them
back?
Thanks
Steve
next reply other threads:[~2010-03-05 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 19:38 Steve Teale [this message]
2010-03-06 0:26 ` Ian Lance Taylor
2010-03-06 7:59 ` Steve Teale
2010-03-08 14:33 ` Ian Lance Taylor
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=1267817886.20422.4.camel@Ubuntu \
--to=steve.teale@britseyeview.com \
--cc=gcc-help@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).