public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109788] [14 Regression] gcc/hwint.h:293:61: runtime error: shift exponent 64 is too large for 64-bit type 'long unsigned int since r14-377-gc92b8be9b52b7e Date: Tue, 09 May 2023 12:31:37 +0000 [thread overview] Message-ID: <bug-109788-4-rnat73vDOV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109788-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109788 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[14 Regression] |[14 Regression] |gcc/hwint.h:293:61: runtime |gcc/hwint.h:293:61: runtime |error: shift exponent 64 is |error: shift exponent 64 is |too large for 64-bit type |too large for 64-bit type |'long unsigned int |'long unsigned int since | |r14-377-gc92b8be9b52b7e CC| |aldyh at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2023-05-09 Status|UNCONFIRMED |NEW --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Started with r14-377-gc92b8be9b52b7e.
next prev parent reply other threads:[~2023-05-09 12:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-09 12:17 [Bug tree-optimization/109788] New: [14 Regression] gcc/hwint.h:293:61: runtime error: shift exponent 64 is too large for 64-bit type 'long unsigned int marxin at gcc dot gnu.org 2023-05-09 12:31 ` marxin at gcc dot gnu.org [this message] 2023-05-09 12:44 ` [Bug tree-optimization/109788] [14 Regression] gcc/hwint.h:293:61: runtime error: shift exponent 64 is too large for 64-bit type 'long unsigned int since r14-377-gc92b8be9b52b7e jakub at gcc dot gnu.org 2023-05-09 12:58 ` [Bug fortran/109788] " jakub at gcc dot gnu.org 2023-05-09 13:10 ` jakub at gcc dot gnu.org 2023-05-10 7:05 ` rguenth at gcc dot gnu.org 2023-05-10 11:21 ` cvs-commit at gcc dot gnu.org 2023-05-10 11:23 ` jakub at gcc dot gnu.org 2023-05-10 18:47 ` anlauf at gcc dot gnu.org 2023-05-10 18:53 ` jakub at gcc dot gnu.org 2023-05-10 18:55 ` jakub at gcc dot gnu.org 2023-05-10 21:40 ` anlauf at gcc dot gnu.org 2023-05-10 21:46 ` jakub at gcc dot gnu.org 2023-05-12 19:41 ` anlauf at gcc dot gnu.org 2023-05-17 8:44 ` jamborm at gcc dot gnu.org 2023-10-17 10:34 ` rguenth at gcc dot gnu.org 2024-05-07 7:40 ` [Bug fortran/109788] [14/15 " 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-109788-4-rnat73vDOV@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).