public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/109886] UBSAN error: shift exponent 64 is too large for 64-bit type when compiling gcc.c-torture/compile/pr96796.c Date: Thu, 08 Jun 2023 19:00:49 +0000 [thread overview] Message-ID: <bug-109886-4-r2aHhTo63u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109886-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109886 --- Comment #8 from Andrew Macleod <amacleod at redhat dot com> --- I just checked in: commit cd9c7f898d6e6313465f78227e566f27dce5e5a3 Author: Andrew MacLeod <amacleod@redhat.com> Date: Wed May 31 13:10:31 2023 -0400 Provide a new dispatch mechanism for range-ops. As a side effect it should make range_cast simply return varying if the RHS is an unsupported type or unimplemented cast. Check if this resolves this PR.
next prev parent reply other threads:[~2023-06-08 19:00 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 8:55 [Bug ipa/109886] New: " jamborm at gcc dot gnu.org 2023-05-17 19:07 ` [Bug ipa/109886] " pinskia at gcc dot gnu.org 2023-05-22 18:04 ` aldyh at gcc dot gnu.org 2023-05-22 18:07 ` pinskia at gcc dot gnu.org 2023-05-22 18:13 ` aldyh at gcc dot gnu.org 2023-05-23 16:14 ` jamborm at gcc dot gnu.org 2023-06-07 20:57 ` amacleod at redhat dot com 2023-06-08 12:27 ` jamborm at gcc dot gnu.org 2023-06-08 19:00 ` amacleod at redhat dot com [this message] 2023-06-09 9:00 ` jamborm at gcc dot gnu.org 2023-06-09 13:14 ` amacleod at redhat dot com 2023-06-09 13:58 ` amacleod at redhat dot com 2023-06-09 16:37 ` cvs-commit at gcc dot gnu.org 2023-06-10 1:44 ` amacleod at redhat dot com 2023-06-13 9:16 ` jamborm 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-109886-4-r2aHhTo63u@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).