public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: What to remove after tree-ssa is merged?
Date: Wed, 04 Feb 2004 16:39:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0402041722310.26764@wotan.suse.de> (raw)
In-Reply-To: <10402041617.AA01497@vlsi1.ultra.nyu.edu>

Hi,

On Wed, 4 Feb 2004, Richard Kenner wrote:

> Looking into a type, yes, but I'm not sure what you mean by "bounded array".

Hmm, in your example you used a type representing an array with bounds.

>     So in that example the P_E is used in expressions, so they could be
>     lowered to trees not containing P_E (this involves probably making
>     some element references more explicit).  
> 
> But you don't have the *object* to make it more explicit when it's
> inside the type.  That's the whole point: it applies to every *object*
> of the type.

Of course.  But somewhen you _do_ apply it to an object.  Otherwise it
wouldn't have any observable effect and you couldn't lower it to RTL.  
And then it can be equally well lowered to trees.

>     To that question you then mentioned P_E inside types, but they should only
>     matter for type comparing or in context of expressions AFAICS.  
> 
>     the latter can be done with the above frontend specific lowering.
> 
> No, because it has to be done by the code that computes sizes and offsets
> in the middle end.

Sure, all expressions involving any P_E recursively would have to be 
expanded in the frontend, including such expressions (probably by using 
temporaries in order not to have to lower the whole tree).  If that's 
feasible I don't know.


Ciao,
Michael.

  reply	other threads:[~2004-02-04 16:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 16:14 Richard Kenner
2004-02-04 16:39 ` Michael Matz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-04 21:55 Richard Kenner
2004-02-04 21:25 Richard Kenner
2004-02-04 21:51 ` Paul Brook
2004-02-04 21:09 Richard Kenner
2004-02-05  5:32 ` Richard Henderson
2004-02-05  5:50   ` Geert Bosch
2004-02-04 20:55 Richard Kenner
2004-02-04 21:21 ` Paul Brook
2004-02-04 18:43 Richard Kenner
2004-02-04 19:49 ` Paul Brook
2004-02-04 20:15   ` Richard Henderson
2004-02-04 17:54 Richard Kenner
2004-02-04 18:39 ` Paul Brook
2004-02-04 15:49 Richard Kenner
2004-02-04 16:10 ` Michael Matz
2004-02-04 17:25 ` Robert Dewar
2004-02-04 15:21 Richard Kenner
2004-02-04 15:19 Richard Kenner
2004-02-04 15:31 ` Michael Matz
2004-02-04 15:16 S. Bosscher
2004-02-04 14:48 Richard Kenner
2004-02-04 14:36 Richard Kenner
2004-02-04 14:44 ` Andrew Pinski
2004-02-04 15:15 ` Michael Matz
2004-02-04 13:52 Richard Kenner
2004-02-04 13:29 S. Bosscher
2004-02-04 13:49 ` Paul Brook
2004-02-04 14:04 ` Michael Matz
2004-02-04 14:19   ` Robert Dewar
2004-02-04 14:31     ` Andrew Pinski
2004-02-04 14:53       ` Robert Dewar
2004-02-04 12:30 Richard Kenner
2004-02-03 16:20 "Documentation by paper" Richard Kenner
2004-02-03 16:54 ` Jan Hubicka
2004-02-03 16:58   ` What to remove after tree-ssa is merged? Paolo Bonzini

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.0402041722310.26764@wotan.suse.de \
    --to=matz@suse.de \
    --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).