From: Richard Henderson <rth@cygnus.com>
To: Alexandre Petit-Bianco <apbianco@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: Proposed new tree node for gcc
Date: Wed, 25 Mar 1998 16:30:00 -0000 [thread overview]
Message-ID: <19980325163115.42437@dot.cygnus.com> (raw)
In-Reply-To: <199803242051.MAA20731@sendai.cygnus.com.>
On Tue, Mar 24, 1998 at 12:51:48PM -0800, Alexandre Petit-Bianco wrote:
> We (Per Bothner and myself) propose the definition of a new tree node
> called EXPR_WITH_FILE_LOCATION defined as a 'e' node. The struct
> tree_exp is big enough to provide us with the appropriate storage
> space: `operands[]' can be used to store the encapsulated node,
> `complexity' is big enough to store line (20 bit) and column numbers
> (12 bit); `common.chain' can provide a hook for filename information.
While I think that the idea is good, doing such gross things with
overloading `common.chain' is very bad. Defining a new struct is
not so difficult, and should be the way this is accomplished.
r~
next prev parent reply other threads:[~1998-03-25 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-24 14:49 Alexandre Petit-Bianco
1998-03-25 16:30 ` Richard Henderson [this message]
1998-03-27 15:18 ` Per Bothner
1998-03-26 21:49 ` Jeffrey A Law
1998-03-29 5:14 ` Per Bothner
1998-03-31 0:46 ` Jeffrey A Law
1998-03-31 0:20 ` Per Bothner
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=19980325163115.42437@dot.cygnus.com \
--to=rth@cygnus.com \
--cc=apbianco@cygnus.com \
--cc=egcs@cygnus.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).