public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nshead at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/114320] New test case in r14-9439-g4aa87b856067d4 fails Date: Mon, 18 Mar 2024 13:46:00 +0000 [thread overview] Message-ID: <bug-114320-4-ygtegIRT7u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114320-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114320 Nathaniel Shead <nshead at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Nathaniel Shead <nshead at gcc dot gnu.org> --- (In reply to Kewen Lin from comment #3) > (In reply to Nathaniel Shead from comment #2) > > Sorry about that. I've not been able to work out what configure flags I need > > to pass to cause this to error in the first place (I don't normally develop > > for powerpc and the machine I'm using doesn't seem to fail no matter what > > I guess the machine you are using (were referring to) isn't with powerpc > chip, cfarm provides some powerpc machines > (https://portal.cfarm.net/machines/list/), both ppc64le (LE -m64) and ppc64 > (BE -m32/-m64), it's recommended to leverage them for building/testing. :) > Thanks; I was actually using one of the cfarm machines (cfarm120 specifically), but on trying a different one I got the errors reported above, and confirmed that adding '-Wno-psabi' fixed them. > > flags I try), but am I correct in understanding that just adding > > "-Wno-psabi" to the tests should stop them from failing? If so I'm happy to > > push a patch to that effect. > > I think so, for now we don't have an effective target dedicated for __ibm128 > type but it's guarded the same as what's for __float128 type (it would be > relaxed though in future, even with that using ppc_float128_sw should just > be more strict). Ideally we can add one effective target powerpc_vsx_ok > (should be powerpc_vsx) to ensure VSX to be enabled, but considering we are > going to rework it in next release and we don't normally disable vsx > explicitly, this can be optional. Thanks, tested and committed as above. Should be fixed.
next prev parent reply other threads:[~2024-03-18 13:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-12 20:18 [Bug testsuite/114320] New: " seurer at gcc dot gnu.org 2024-03-13 1:54 ` [Bug testsuite/114320] " linkw at gcc dot gnu.org 2024-03-15 13:03 ` nshead at gcc dot gnu.org 2024-03-18 2:03 ` linkw at gcc dot gnu.org 2024-03-18 13:42 ` cvs-commit at gcc dot gnu.org 2024-03-18 13:46 ` nshead at gcc dot gnu.org [this message] 2024-03-18 13:46 ` nshead 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-114320-4-ygtegIRT7u@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).