public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108623] We need to grow the precision field in tree_type_common for PowerPC Date: Wed, 01 Feb 2023 08:21:41 +0000 [thread overview] Message-ID: <bug-108623-4-aa1xiscG51@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108623-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108623 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Note there's code that might need adjustments. We for example have /* Return the number of elements in the VECTOR_TYPE given by NODE. */ inline poly_uint64 TYPE_VECTOR_SUBPARTS (const_tree node) { STATIC_ASSERT (NUM_POLY_INT_COEFFS <= 2); unsigned int precision = VECTOR_TYPE_CHECK (node)->type_common.precision; if (NUM_POLY_INT_COEFFS == 2) { /* See the corresponding code in SET_TYPE_VECTOR_SUBPARTS for a description of the encoding. */ poly_uint64 res = 0; res.coeffs[0] = HOST_WIDE_INT_1U << (precision & 0xff); if (precision & 0x100) res.coeffs[1] = HOST_WIDE_INT_1U << (precision & 0xff); return res; } which looks odd anyways. Richard might know where the 10 bits have been baked in to (ISTR something about the INTEGER_CST encoding stuff here with the three kinds of "precisions")
next prev parent reply other threads:[~2023-02-01 8:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-01 8:00 [Bug other/108623] New: " meissner at gcc dot gnu.org 2023-02-01 8:18 ` [Bug middle-end/108623] " rguenth at gcc dot gnu.org 2023-02-01 8:21 ` rguenth at gcc dot gnu.org [this message] 2023-02-01 10:16 ` rsandifo at gcc dot gnu.org 2023-02-01 16:48 ` meissner at gcc dot gnu.org 2023-02-01 17:32 ` segher at gcc dot gnu.org 2023-02-01 17:37 ` meissner at gcc dot gnu.org 2023-02-01 17:40 ` meissner at gcc dot gnu.org 2023-02-01 18:52 ` joseph at codesourcery dot com 2023-02-02 8:22 ` rguenther at suse dot de 2023-02-02 9:04 ` rsandifo at gcc dot gnu.org 2023-05-08 12:03 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:05 ` 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-108623-4-aa1xiscG51@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).