public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/58429] New: _Decimal64 support is broken on powerpc64 with the mode32 ABI (-m32 -mpowerpc64) Date: Sun, 15 Sep 2013 23:02:00 -0000 [thread overview] Message-ID: <bug-58429-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58429 Bug ID: 58429 Summary: _Decimal64 support is broken on powerpc64 with the mode32 ABI (-m32 -mpowerpc64) Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vincent-gcc at vinc17 dot net On gcc110.fsffrance.org: $ cat ./decimal64.c #include <stdio.h> int main(void) { _Decimal64 x = 1; if (x != x) { printf ("Error!\n"); return 1; } else { printf ("OK\n"); return 0; } } $ gcc -Wall -std=gnu99 -m32 -mpowerpc64 decimal64.c -o decimal64 -O $ ./decimal64 OK $ gcc -Wall -std=gnu99 -m32 -mpowerpc64 decimal64.c -o decimal64 $ ./decimal64 Error! (The lack of error with -O is due to obvious optimization; a "volatile" on the variable makes the error appear in every case.) The problem doesn't appear with -m32 alone or -mpowerpc64 alone. Both are needed to make it appear. $ gcc --version gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8) Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2013-09-15 23:02 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-15 23:02 vincent-gcc at vinc17 dot net [this message] 2021-08-16 5:34 ` [Bug target/58429] " pinskia 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-58429-4@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: 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).