From: shaurya arora <arora@gdit.iiit.net>
To: <gcc@gcc.gnu.org>
Subject: Re: Remove reference to nonexistent TYPE_* macros from tree.def
Date: Mon, 28 Oct 2002 07:37:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0210280151530.1881-100000@gdit.iiit.net> (raw)
I had just posted the same question before i saw this. so i guess this had
already answered my question.
Anyone know the story behind this ? I mean why was TYPE_SEP put and then
not used ? I was planning on using this field assuming that this would be
used during RTL generation, I guess ill now have to figure out another way
to place fields in an array such that their separation is different from
the sizeof each field. :(
shaurya
>tree.def makes reference to TYPE_SEP and TYPE_SEP_UNIT, which are
>nowhere in the code, nor are they mentioned in the change logs. This
>patch removes the references.
>
>Applied as obvious.
>
>zw
reply other threads:[~2002-10-27 20:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.33.0210280151530.1881-100000@gdit.iiit.net \
--to=arora@gdit.iiit.net \
--cc=gcc@gcc.gnu.org \
/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).