public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tenthumbs@cybernex.net
To: gcc-gnats@gcc.gnu.org
Subject: optimization/8278: gcc3.2 -O3 generates wrong code
Date: Fri, 18 Oct 2002 12:36:00 -0000	[thread overview]
Message-ID: <20021018193249.20069.qmail@sources.redhat.com> (raw)


>Number:         8278
>Category:       optimization
>Synopsis:       gcc3.2 -O3 generates wrong code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 18 12:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     tenthumbs@cybernex.net
>Release:        unknown-1.0
>Organization:
>Environment:
Linux x86
>Description:
Compile the attached code with -O2 and then with -O3 and
note the different output. It appears the gcc pushes the
printf arguments in the wrong order.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="q.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="q.c"

I2luY2x1ZGUgPHN0ZGlvLmg+CgppbnQgZnJvYiAoaW50IHgpCnsKCXJlZ2lzdGVyIGludCByOwoK
CWFzbSB2b2xhdGlsZSAoCgkJInNocmwgJDMxLCAlJWVheFxuXHQiCgkJOiAiPXIiIChyKQoJCTog
IjAiICh4KQoJKTsKCXJldHVybiByOwp9CgpzdGF0aWMgY29uc3QgaW50IGludHNbXSA9IHsxLC0x
LDEyMzQ1LC0xMjM0NSwgMCwgMHg4MDAwMDAwMCwgMHg3ZmZmZmZmZn07CnN0YXRpYyBjb25zdCBp
bnQgbmludHMgPSBzaXplb2YoaW50cykvc2l6ZW9mKGludHNbMF0pOwoKaW50IG1haW4gKHZvaWQp
CnsKCWludCBpOwoKCWZvciAoaSA9IDA7IGkgPCBuaW50czsgKytpKQoJewoJCXByaW50ZiAoIiVk
IC0+ICVkXG4iLCBpbnRzW2ldLCBmcm9iKGludHNbaV0pKTsKCX0KCXJldHVybiAwOwp9Cg==


             reply	other threads:[~2002-10-18 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 12:36 tenthumbs [this message]
2002-10-22  0:08 rth
2003-02-23 21:04 neroden

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=20021018193249.20069.qmail@sources.redhat.com \
    --to=tenthumbs@cybernex.net \
    --cc=gcc-gnats@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).