From: "Chris Li" <christ.li@gmail.com>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: David Given <dg@cowlark.com>, linux-sparse@vger.kernel.org
Subject: Re: Adding type information to instructions
Date: Mon, 7 Jul 2008 13:08:08 -0700 [thread overview]
Message-ID: <70318cbf0807071308i5ce33e92rf7b033d5709da2a2@mail.gmail.com> (raw)
In-Reply-To: <1215452561.3003.21.camel@josh-work.beaverton.ibm.com>
On Mon, Jul 7, 2008 at 10:42 AM, Josh Triplett <josht@linux.vnet.ibm.com> wrote:
> I can't think of any fundamental reason not to do this, other than the
> standard reason of data structure size.
There is other ways to avoid the size blow up. At the linearized byte
code level,
the back end only need to know it is one of the stander C type . So we have an
array of stander ctype C type similar to ctype_declaration[].
We just need to replace the size member with the array index in the instruction
struct..
Chris
prev parent reply other threads:[~2008-07-07 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 23:43 Adding type information to instructions David Given
2008-07-07 17:42 ` Josh Triplett
2008-07-07 20:08 ` Chris Li [this message]
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=70318cbf0807071308i5ce33e92rf7b033d5709da2a2@mail.gmail.com \
--to=christ.li@gmail.com \
--cc=dg@cowlark.com \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).