public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/101002] New: Some powerpc tests fail with -mlong-double-64 Date: Wed, 09 Jun 2021 20:18:30 +0000 [thread overview] Message-ID: <bug-101002-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101002 Bug ID: 101002 Summary: Some powerpc tests fail with -mlong-double-64 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: meissner at gcc dot gnu.org Target Milestone: --- I now build GCC with all 3 long double variants (IEEE 128-bit, IBM 128-bit, and 64-bit). The following C test fail when when you configure the compiler to use 64-bit long doubles: gcc.dg/float128-align.c gcc.dg/float64x-align.c gcc.dg/tree-ssa/builtin-sprintf.c gcc.target/powerpc/convert-fp-64.c gcc.target/powerpc/float128-hw.c gcc.target/powerpc/float128-hw4.c gcc.target/powerpc/gnuattr2.c gcc.target/powerpc/gnuattr3.c gcc.target/powerpc/pr60203.c gcc.target/powerpc/pr79004.c gcc.target/powerpc/pr82748-1.c gcc.target/powerpc/pr85657-3.c gcc.target/powerpc/signbit-1.c
next reply other threads:[~2021-06-09 20:18 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-09 20:18 meissner at gcc dot gnu.org [this message] 2021-06-10 15:17 ` [Bug testsuite/101002] " bergner at gcc dot gnu.org 2021-06-11 20:54 ` segher at gcc dot gnu.org 2021-06-11 20:55 ` segher at gcc dot gnu.org 2023-06-20 21:20 ` bergner at gcc dot gnu.org 2023-06-21 17:30 ` bergner at gcc dot gnu.org 2023-06-21 17:41 ` bergner at gcc dot gnu.org 2023-06-21 20:31 ` bergner at gcc dot gnu.org 2023-06-21 20:34 ` bergner at gcc dot gnu.org 2023-06-21 23:19 ` segher at gcc dot gnu.org 2023-06-22 13:49 ` dje 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-101002-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).