public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mattias@virtutech.se To: gcc-gnats@gcc.gnu.org Cc: gustav@virtutech.se Subject: target/6981: wrong code in 64-bit manipulation on x86 Date: Mon, 10 Jun 2002 02:56:00 -0000 [thread overview] Message-ID: <20020610095206.12539.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1872 bytes --] >Number: 6981 >Category: target >Synopsis: wrong code in 64-bit manipulation on x86 >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Mon Jun 10 02:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Mattias Engdegård >Release: gcc version 3.1 >Organization: >Environment: redhat 6.2 host (x86) >Description: gcc 3.1 (x86 target) generates wrong code when the attached file is compiled with -O2. The error is in the bar() function. The attach file also serves as a testcase, returning 0 if the bug is present, 1 otherwise. (What makes the problem severe is that the wrong code is generated silently and the exact circumstances unknown, so we are going back to 3.0.4 meanwhile.) >How-To-Repeat: Compile the attached file with -O2, using plain gcc 3.1 for x86, built from source with a default configuration. >Fix: Use a lower optimisation level than -O2 >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="sr1.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="sr1.c" dHlwZWRlZiB1bnNpZ25lZCBsb25nIGxvbmcgdWludDY0OwoKdWludDY0ICpjcDsKdWludDY0IG07 Cgp2b2lkIGZvbyh2b2lkKQp7Cn0KCnZvaWQgYmFyKHVuc2lnbmVkIHJvcCwgdWludDY0ICpyKQp7 Cgl1bnNpZ25lZCByczEsIHJzMiwgcmQ7CgogdG9wOgoJcnMyID0gKHJvcCA+PiAyMykgJiAweDFm ZjsKCXJzMSA9IChyb3AgPj4gOSkgJiAweDFmZjsKCXJkID0gcm9wICYgMHgxZmY7CgoJKmNwID0g MTsKCW0gPSByW3JzMV0gKyByW3JzMl07CgkqY3AgPSAyOwoJZm9vKCk7CglpZiAoIXJkKQoJCWdv dG8gdG9wOwoJcltyZF0gPSAxOwp9CgppbnQgbWFpbih2b2lkKQp7CglzdGF0aWMgdWludDY0IHJb NjRdOwoJdWludDY0IGNyOwoJY3AgPSAmY3I7CgkKCXJbNF0gPSA0NzsKCXJbOF0gPSAxMTsKCWJh cigoOCA8PCAyMykgfCAoNCA8PCA5KSB8IDE1LCByKTsKCQoJcmV0dXJuIG0gPT0gNDcgKyAxMSA/ IDAgOiAxOwp9Cg==
next reply other threads:[~2002-06-10 9:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-10 2:56 mattias [this message] 2002-07-16 6:56 Mattias Engdegård 2002-07-25 8:06 Mattias Engdegård 2002-07-26 8:26 jakub 2002-10-24 12:00 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=20020610095206.12539.qmail@sources.redhat.com \ --to=mattias@virtutech.se \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gustav@virtutech.se \ /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: linkBe 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).