From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: jsm@polyomino.org.uk
Cc: gcc@gcc.gnu.org
Subject: Re: SRA problem with uninitialzed fields
Date: Fri, 24 Sep 2004 18:53:00 -0000 [thread overview]
Message-ID: <10409241623.AA01865@vlsi1.ultra.nyu.edu> (raw)
A proper implementation that keeps the types those that accord with
the language semantics would be for the GIMPLE generated to include
explicit mask operations for assignments to bit-fields. If it doesn't
represent that assignment to a bit-field from the same type may change
the value, then there are likely to be problems. At one point there
were, but I don't see such problems at present in some quick tests.
Well, look at the test case I sent. A mask is clearly required on the
comparison (at least, I think so!), but the only mechanism to generate it
is the hook, which is false for C++.
next reply other threads:[~2004-09-24 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 18:53 Richard Kenner [this message]
2004-09-24 19:02 ` Joseph S. Myers
2004-09-25 2:38 ` Robert Dewar
2004-09-25 2:59 ` Joseph S. Myers
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 18:43 Richard Kenner
2004-09-24 18:50 ` Joseph S. Myers
2004-09-24 16:55 Richard Kenner
2004-09-24 18:23 ` Joseph S. Myers
2004-09-24 16:01 Richard Kenner
2004-09-24 16:16 ` Andrew Pinski
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=10409241623.AA01865@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
/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).