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/96139] Vector element extract mistypes long long int down to long int Date: Tue, 15 Sep 2020 21:46:33 +0000 [thread overview] Message-ID: <bug-96139-4-L3InHFbJu1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96139-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96139 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Will Schmidt <willschm@gcc.gnu.org>: https://gcc.gnu.org/g:04a9b796436c68a07c052805631e962a1126dcca commit r9-8872-g04a9b796436c68a07c052805631e962a1126dcca Author: Will Schmidt <will_schmidt@vnet.ibm.com> Date: Tue Sep 15 15:06:08 2020 -0500 [PATCH, rs6000] Fix vector long long subtype (PR96139) Hi, This corrects an issue with the powerpc vector long long subtypes. As reported by SjMunroe, when building some code with -Wall, and attempting to print an element of a "long long vector" with a long long printf format string, we will report an error because the vector sub-type was improperly defined as int. When defining a V2DI_type_node we use a TARGET_POWERPC64 ternary to define the V2DI_type_node with "vector long" or "vector long long". We also need to specify the proper sub-type when we define the type. Due to some file renames, This is a backport and rework of both [PATCH, rs6000] Fix vector long long subtype (PR96139) and [PATCH, rs6000] Testsuite fixup pr96139 tests PR target/96139 2020-09-03 Will Schmidt <will_schmidt@vnet.ibm.com> gcc/ChangeLog: * config/rs6000/rs6000.c (rs6000_init_builtin): Update V2DI_type_node and unsigned_V2DI_type_node definitions. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr96139-a.c: New test. * gcc.target/powerpc/pr96139-b.c: New test. * gcc.target/powerpc/pr96139-c.c: New test.
next prev parent reply other threads:[~2020-09-15 21:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-09 19:44 [Bug c/96139] New: " munroesj at gcc dot gnu.org 2020-07-09 20:05 ` [Bug c/96139] " munroesj at gcc dot gnu.org 2020-07-09 22:01 ` [Bug target/96139] " wschmidt at gcc dot gnu.org 2020-07-10 0:34 ` munroesj at gcc dot gnu.org 2020-07-10 7:28 ` rguenth at gcc dot gnu.org 2020-07-16 23:03 ` willschm at gcc dot gnu.org 2020-09-03 20:11 ` cvs-commit at gcc dot gnu.org 2020-09-15 17:17 ` cvs-commit at gcc dot gnu.org 2020-09-15 20:50 ` willschm at gcc dot gnu.org 2020-09-15 21:46 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-15 22:13 ` willschm at gcc dot gnu.org 2020-09-16 16:28 ` cvs-commit 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-96139-4-L3InHFbJu1@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).