From: Mark Mitchell <mark@codesourcery.com>
To: Kenneth Zadeck <zadeck@naturalbridge.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: potiential problems with parm decls.
Date: Thu, 02 Aug 2007 02:50:00 -0000 [thread overview]
Message-ID: <46B14662.50002@codesourcery.com> (raw)
In-Reply-To: <46B12F18.6080707@naturalbridge.com>
Kenneth Zadeck wrote:
> 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.
No, they are CONSTRUCTOR trees, whose CONSTRUCTOR_ELEMENTS are also
trees, like INTEGER_CSTs or STRING_CSTs. I'd imagine that since you
have routines to write out trees, recursively, these should be pretty
easy; at worst, we'd have to add support for CONSTRUCTOR, if you don't
already have it.
Does that sound right to you?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2007-08-02 2:50 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
2007-08-02 2:50 ` Mark Mitchell [this message]
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=46B14662.50002@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=zadeck@naturalbridge.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).