From: "Giovanni Bajo" <rasky@develer.com>
To: "Daniel Berlin" <dberlin@dberlin.org>
Cc: <gcc@gcc.gnu.org>, "Richard Henderson" <rth@redhat.com>
Subject: Re: PARM_DECL of DECL_SIZE 0, but TYPE_SIZE of 96 bits
Date: Thu, 30 Jun 2005 18:48:00 -0000 [thread overview]
Message-ID: <071801c57da4$3986c7d0$bf03030a@trilan> (raw)
In-Reply-To: <1120085832.7612.81.camel@linux-009002219098>
Daniel Berlin <dberlin@dberlin.org> wrote:
> So we've got a parm decl that if you ask it for the DECL_SIZE, says 0,
> but has a TYPE_SIZE of 12 bytes, and we access fields in it, etc.
I am not sure of what the exact relations between DECL_SIZE and TYPE_SIZE
are, but probably some verification could be done, eg, at gimplification
time, rather than waiting for latent bugs in optimizers to produce wrong
code?
--
Giovanni Bajo
next prev parent reply other threads:[~2005-06-30 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 22:57 Daniel Berlin
2005-06-29 23:55 ` Richard Henderson
2005-06-30 1:17 ` Daniel Berlin
2005-06-30 4:35 ` [C++] " Richard Henderson
2005-06-30 21:12 ` Geoffrey Keating
2005-07-01 1:47 ` Daniel Berlin
2005-07-05 6:25 ` Mark Mitchell
2005-07-05 15:35 ` Mark Mitchell
2005-07-05 16:18 ` Daniel Berlin
2005-06-30 18:48 ` Giovanni Bajo [this message]
2005-06-30 19:02 ` Daniel Berlin
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='071801c57da4$3986c7d0$bf03030a@trilan' \
--to=rasky@develer.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).