public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57347] [4.8/4.9 Regression] wrong code for bitfield on x86_64-linux at -Os and above
Date: Tue, 21 May 2013 12:26:00 -0000	[thread overview]
Message-ID: <bug-57347-4-8HcjevWQES@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57347-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57347

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jamborm at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't find code in http://gcc.gnu.org/ml/gcc-patches/2012-11/msg00460.html to
handle bitfields, the comment talks about punting on them, but I couldn't find
anything that would try to punt.
ipa_load_from_parm_agg_1 seems to return just the bit offset (which is then
compared to the offsets in aggval chain), but not the access bitsize (if aggval
is guaranteed to contain values for all fields, then perhaps with bitsize it
would be enough to look for all v where v->offset is in [offset,
offset+bitsize)
and combine all those values together - is v->value always constant?).


  parent reply	other threads:[~2013-05-21 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 23:28 [Bug rtl-optimization/57347] New: " dhazeghi at yahoo dot com
2013-05-21  6:32 ` [Bug rtl-optimization/57347] [4.8/4.9 Regression] " jakub at gcc dot gnu.org
2013-05-21 12:26 ` jakub at gcc dot gnu.org [this message]
2013-05-21 13:47 ` jamborm at gcc dot gnu.org
2013-05-23 13:47 ` [Bug middle-end/57347] " jamborm at gcc dot gnu.org
2013-05-23 13:47 ` jamborm at gcc dot gnu.org

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=bug-57347-4-8HcjevWQES@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).