public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jakub@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, namsh@kldp.org,
	nobody@gcc.gnu.org
Subject: Re: optimization/6673: gcc-3.1 produces wrong assembly code
Date: Thu, 16 May 2002 06:40:00 -0000	[thread overview]
Message-ID: <20020516134014.22483.qmail@sources.redhat.com> (raw)

Synopsis: gcc-3.1 produces wrong assembly code

State-Changed-From-To: open->feedback
State-Changed-By: jakub
State-Changed-When: Thu May 16 06:40:11 2002
State-Changed-Why:
    Why do you think this is wrong?
    If there is no volatile, there is nothing which prevents
    gcc e.g. with ++a; ++a; ++a to do all the additions at
    once and store just the final result. Similarly with your
    testcase, gcc does all additions together and stores the
    end result after all infinity iterations. Since the loop
    will never finish, gcc can as well optimize the final
    store out.

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


             reply	other threads:[~2002-05-16 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16  6:40 jakub [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-16 22:26 Nam SungHyun
2002-05-16 22:06 Richard Henderson
2002-05-16 21:56 Nam SungHyun
2002-05-16 19:12 rth
2002-05-16  3:46 namsh

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=20020516134014.22483.qmail@sources.redhat.com \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=namsh@kldp.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).