public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51534] Bad code gen for vcgtq_u32 NEON intrinsic Date: Fri, 03 Mar 2023 19:10:10 +0000 [thread overview] Message-ID: <bug-51534-4-OHII04aTz4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51534-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51534 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:cc9cc5a9a5fb0c16532a16b87fbd155037a7ed89 commit r13-6457-gcc9cc5a9a5fb0c16532a16b87fbd155037a7ed89 Author: Alexandre Oliva <oliva@adacore.com> Date: Fri Mar 3 15:59:21 2023 -0300 [PR51534] [arm] split out pr51534 test for softfp The test uses arm_hard_ok and arm_softfp_ok as if they were mutually exclusive, but they test whether the corresponding -mfloat-abi= flag is usable, not whether it is in effect, so it is possible for both to pass, and then the test comes out with incorrect expectations whichever the default float-abi is. Separate the test into hard and softfp variants, and extend the softfp variant to accept both ARM and Thumb opcodes; it unwarrantedly assumed the latter. for gcc/testsuite/ChangeLog PR target/51534 * gcc.target/arm/pr51534.c: Split softfp variant into... * gcc.target/arm/pr51534s.c: ... this, and support ARM too.
prev parent reply other threads:[~2023-03-03 19:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-13 19:29 [Bug target/51534] New: " rmansfield at qnx dot com 2011-12-13 19:53 ` [Bug target/51534] " rmansfield at qnx dot com 2011-12-14 15:01 ` rearnsha at gcc dot gnu.org 2012-02-28 16:15 ` mgretton at gcc dot gnu.org 2012-02-28 16:19 ` mgretton at gcc dot gnu.org 2014-08-10 16:46 ` rmansfield at qnx dot com 2023-03-03 19:10 ` cvs-commit at gcc dot gnu.org [this message]
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-51534-4-OHII04aTz4@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).