public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: potiential problems with parm decls.
Date: Thu, 02 Aug 2007 01:10:00 -0000	[thread overview]
Message-ID: <46B12F18.6080707@naturalbridge.com> (raw)
In-Reply-To: <46B128AF.5080008@codesourcery.com>

Mark Mitchell wrote:
> Kenneth Zadeck wrote:
>
>   
>> My only concern here is that you said at the summit that these were not
>> in gimple.  If they are in gimple, then it should not be a big deal for
>> me to co-opt the existing machinery to put each of them in its own
>> section. 
>>     
>
> I'm not sure "being GIMPLE" has meaning in this context; they're just
> data.  The expressions are all constants, like "3", "&foo", or "&foo +
> 1".  These can be arranged in aggregates; you can have a CONSTRUCTOR
> whose elements are "3" and "&foo", for example.  Will that work?
>
> Thanks,
>
>   
i think that the short answer is that they are not gimple.

I have a way to put out counted strings.  I assume that each of these is
just an list (or array) of counted strings.  If that is all, (i.e. there
is not any deeper structure) then I can look into it. 

Give me some pointers so i can figure out the datastructures i need to
walk and rebuild.

kenny.

  reply	other threads:[~2007-08-02  1:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 14:16 Kenneth Zadeck
2007-08-01 17:23 ` Mark Mitchell
2007-08-01 17:34   ` Kenneth Zadeck
2007-08-02  0:43     ` Mark Mitchell
2007-08-02  1:10       ` Kenneth Zadeck [this message]
2007-08-02  2:50         ` Mark Mitchell
2007-08-01 20:44   ` [lto] PATCH COMMITTED " Kenneth Zadeck
2007-08-01 22:12     ` Tom Tromey
2007-08-01 22:36       ` Kenneth Zadeck
2007-08-02  1:06       ` [lto] PATCH COMMITTED to fix missing semicolons Kenneth Zadeck
2007-08-02  1:16         ` David Daney
2007-08-02  1:49           ` Andrew Pinski
2007-08-02 16:42             ` Kenneth Zadeck

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=46B12F18.6080707@naturalbridge.com \
    --to=zadeck@naturalbridge.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).