public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/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:58:10 +0000 [thread overview] Message-ID: <bug-109788-4-N9y0AuW9rm@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|tree-optimization |fortran --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ah, perhaps it is a Fortran FE bug, but still IPA should try to be careful. The _gfortran_spread_char_scalar fndecl the FE creates has types array01_character(kind=1)&, integer(kind=8), real(kind=4)&, integer(kind=8)&, integer(kind=4)& (just 5 arguments), but the call passes it 6 arguments, which is why param_type for the last one is VOID_TYPE (aka the argument type list terminator). Strangely, the libgfortran function it is actually calling has void spread_char_scalar (gfc_array_char *ret, GFC_INTEGER_4 ret_length __attribute__((unused)), const char *source, const index_type *along, const index_type *pncopies, GFC_INTEGER_4 source_length __attribute__((unused))) prototype. So, not really sure how can this work at all.
next prev parent reply other threads:[~2023-05-09 12:58 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 ` [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 marxin at gcc dot gnu.org 2023-05-09 12:44 ` jakub at gcc dot gnu.org 2023-05-09 12:58 ` jakub at gcc dot gnu.org [this message] 2023-05-09 13:10 ` [Bug fortran/109788] " 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-N9y0AuW9rm@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).