From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: aph@redhat.com, gcc-patches@gcc.gnu.org, java@gcc.gnu.org
Subject: Re: Patch to allow Ada to work with tree-ssa
Date: Tue, 22 Jun 2004 20:10:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0406221833290.27086@digraph.polyomino.org.uk> (raw)
In-Reply-To: <10406221818.AA08344@vlsi1.ultra.nyu.edu>
On Tue, 22 Jun 2004, Richard Kenner wrote:
> Indeed a number of things I did might have had the effect of changing
> the order in which subtrees are gimplified. Since I didn't think that
> anything depended on that, I didn't pay that much attention to the issue.
> If there are places that do depend on that, can you identify them so
> that comments can be placed in gimplify.c saying what's order-dependent.
We have a flag (flag_evaluation_order) for languages to say whether the
order of evaluation of subexpressions matters (effectively creating two
dialects of GENERIC). Java sets this flag, and it should be followed.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-06-22 18:37 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 19:05 Richard Kenner
2004-06-22 20:10 ` Joseph S. Myers [this message]
2004-06-22 20:27 ` Andrew Haley
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 19:02 Richard Kenner
2004-07-29 18:43 Richard Kenner
2004-07-29 17:12 Richard Kenner
2004-07-29 17:13 ` Diego Novillo
2004-07-29 17:57 ` Richard Henderson
2004-06-25 15:28 Richard Kenner
2004-06-28 15:09 ` Paolo Bonzini
2004-06-24 15:58 Richard Kenner
2004-06-24 16:04 ` Nathan Sidwell
2004-06-25 14:43 ` Joseph S. Myers
2004-06-23 5:54 Richard Kenner
2004-06-23 2:32 Richard Kenner
2004-06-23 4:54 ` Bryce McKinlay
2004-06-23 0:16 Richard Kenner
2004-06-22 23:05 Richard Kenner
2004-06-23 11:42 ` Nathan Sidwell
2004-06-22 22:18 Richard Kenner
2004-06-23 1:07 ` Richard Henderson
2004-06-22 21:30 Richard Kenner
2004-06-22 22:04 ` Paul Brook
2004-06-22 21:27 Richard Kenner
2004-06-22 21:29 ` Mark Mitchell
2004-06-22 21:10 Richard Kenner
2004-06-22 21:12 ` Mark Mitchell
2004-06-22 22:16 ` Daniel Berlin
2004-06-22 21:07 Richard Kenner
2004-06-22 21:12 ` Bryce McKinlay
2004-06-22 21:05 Richard Kenner
2004-06-22 21:01 Richard Kenner
2004-06-22 20:54 Richard Kenner
2004-06-22 21:06 ` Paul Brook
2004-06-22 21:37 ` Richard Henderson
2004-06-22 20:44 Richard Kenner
2004-06-22 21:03 ` Mark Mitchell
2004-06-23 20:58 ` Geoffrey Keating
2004-06-22 20:40 Richard Kenner
2004-06-22 22:02 ` Nathan Sidwell
2004-06-22 22:27 ` Joseph S. Myers
2004-06-22 20:23 Richard Kenner
2004-06-22 20:37 ` Joseph S. Myers
2004-06-23 20:47 ` Geoffrey Keating
2004-06-24 14:59 ` Joseph S. Myers
2004-06-24 16:26 ` Richard Earnshaw
2004-06-24 19:57 ` Laurent GUERBY
2004-06-24 20:06 ` Diego Novillo
2004-06-24 20:24 ` Andrew Pinski
2004-06-24 22:35 ` Laurent GUERBY
2004-06-24 21:33 ` Laurent GUERBY
2004-06-24 21:01 ` Joseph S. Myers
2004-06-25 14:51 ` Richard Earnshaw
2004-06-22 20:22 Richard Kenner
2004-06-22 20:30 ` Mark Mitchell
[not found] <10406221359.AA05860@vlsi1.ultra.nyu.edu>
2004-06-22 18:47 ` Richard Henderson
2004-06-22 18:33 Richard Kenner
2004-06-22 18:19 Richard Kenner
2004-06-22 18:36 ` Nathan Sidwell
2004-06-22 18:37 ` Nathan Sidwell
2004-06-22 18:45 ` Mark Mitchell
2004-06-22 17:05 Richard Kenner
2004-06-22 17:21 ` Andrew Haley
2004-06-22 19:01 ` Richard Henderson
2004-06-22 16:34 Richard Kenner
2004-06-22 16:33 Richard Kenner
2004-06-22 17:46 ` Mark Mitchell
2004-06-22 18:17 ` Joseph S. Myers
2004-06-22 18:52 ` Richard Henderson
2004-06-22 19:37 ` Zack Weinberg
2004-06-22 7:05 Richard Kenner
2004-06-22 7:29 ` Mark Mitchell
2004-06-22 9:14 ` Andrew Pinski
2004-06-22 14:16 ` Andrew Haley
2004-06-22 11:00 ` Richard Henderson
2004-06-22 13:52 ` Ranjit Mathew
2004-07-29 17:02 ` Diego Novillo
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=Pine.LNX.4.58.0406221833290.27086@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java@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).