From: Richard Guenther <rguenther@suse.de>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org, ebotcazou@adacore.com, kenner@vlsi1.ultra.nyu.edu
Subject: Re: [RFH][tuples] Make Ada work
Date: Mon, 21 Jul 2008 12:33:00 -0000 [thread overview]
Message-ID: <alpine.LNX.1.10.0807211423460.4328@zhemvz.fhfr.qr> (raw)
In-Reply-To: <48847412.7000001@google.com>
On Mon, 21 Jul 2008, Diego Novillo wrote:
> On 7/20/08 1:43 PM, Richard Guenther wrote:
>
> > --- 2318,2326 ----
> > for (i = 0; i < gimple_num_ops (s); i++)
> > if (TREE_SIDE_EFFECTS (gimple_op (s, i)))
> > {
> > ! /* FIXME tuples. This assign is over-eager at least
> > ! for Ada.
> > ! gcc_assert (gimple_has_volatile_ops (s)); */
>
> I can't parse the comment. What do you mean by 'This assign is over-eager'?
I fixed the real cause of the asserts triggering. See
http://gcc.gnu.org/ml/gcc-patches/2008-07/msg01545.html
Richard.
prev parent reply other threads:[~2008-07-21 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 18:39 Richard Guenther
2008-07-20 20:09 ` Arnaud Charlet
2008-07-21 12:25 ` Diego Novillo
2008-07-21 12:33 ` Richard Guenther [this message]
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=alpine.LNX.1.10.0807211423460.4328@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=dnovillo@google.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).