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 d/110193] d_signed_or_unsigned_type is invoked for vector types Date: Wed, 28 Jun 2023 15:53:31 +0000 [thread overview] Message-ID: <bug-110193-4-YjMCpW33KL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110193-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110193 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:9757e4440bd8755d327601a60a73d57d712583ed commit r14-2168-g9757e4440bd8755d327601a60a73d57d712583ed Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Wed Jun 28 17:38:16 2023 +0200 d: Fix d_signed_or_unsigned_type is invoked for vector types (PR110193) This function can be invoked on VECTOR_TYPE, but the implementation assumes it works on integer types only. To fix, added a check whether the type passed is any `__vector(T)' or non-integral type, and return early by calling `signed_or_unsigned_type_for()' instead. Problem was found by instrumenting TYPE_PRECISION and ICEing when applied on VECTOR_TYPEs. PR d/110193 gcc/d/ChangeLog: * types.cc (d_signed_or_unsigned_type): Handle being called with any vector or non-integral type.
next prev parent reply other threads:[~2023-06-28 15:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-09 13:06 [Bug d/110193] New: " rguenth at gcc dot gnu.org 2023-06-09 14:59 ` [Bug d/110193] " pinskia at gcc dot gnu.org 2023-06-10 18:25 ` ibuclaw at gcc dot gnu.org 2023-06-10 18:40 ` ibuclaw at gcc dot gnu.org 2023-06-10 18:42 ` ibuclaw at gcc dot gnu.org 2023-06-12 7:58 ` rguenth at gcc dot gnu.org 2023-06-28 15:53 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-28 16:28 ` ibuclaw at gcc dot gnu.org 2023-06-29 8:16 ` rguenth 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-110193-4-YjMCpW33KL@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).