public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: eriksoe@daimi.au.dk, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: middle-end/9998: Lost update on bitfield manipulation via pointer
Date: Mon, 10 Mar 2003 15:31:00 -0000	[thread overview]
Message-ID: <20030310153135.32685.qmail@sources.redhat.com> (raw)

Synopsis: Lost update on bitfield manipulation via pointer

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Mon Mar 10 15:31:35 2003
State-Changed-Why:
    This was fixed between 3.2 and 3.2.2:
    
    g/x> /home/bangerth/bin/gcc-3.2/bin/gcc -ggdb bug1.i -O2
    g/x> ./a.out
    0
    g/x> /home/bangerth/bin/gcc-3.2.2-pre/bin/gcc -ggdb bug1.i -O2
    g/x> ./a.out
    1
    
    However, you may be violating aliasing rules in your code,
    by accessing an object of type M as an object of type N.
    In fact, with gcc3.0.4, the code works as expected by
    using -fno-strict-aliasing:
    g/x> /home/bangerth/bin/gcc-3.0.4/bin/gcc -ggdb bug1.i -O0 && ./a.out
    1
    g/x> /home/bangerth/bin/gcc-3.0.4/bin/gcc -ggdb bug1.i -O2 && ./a.out
    0
    g/x> /home/bangerth/bin/gcc-3.0.4/bin/gcc -ggdb bug1.i -O2 -fno-strict-aliasing && ./a.out
    1
    
    It might therefore well be that the "fix" between 3.2 and
    3.2.2 just doesn't exercise rights to optimize, with your
    code still being faulty.
    
    3.3 and mainline work, by the way.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9998


             reply	other threads:[~2003-03-10 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 15:31 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-08  6:56 eriksoe

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=20030310153135.32685.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=eriksoe@daimi.au.dk \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).