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 fortran/96024] [10/11/12/13 Regression] ICE in mio_name_expr_t, at fortran/module.c:2159
Date: Fri, 09 Jun 2023 07:21:05 +0000 [thread overview]
Message-ID: <bug-96024-4-JIQmzfgbdz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96024-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96024
--- Comment #20 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:32c51d0911e8d1bdf3f60bc831794b7932416ccd
commit r13-7431-g32c51d0911e8d1bdf3f60bc831794b7932416ccd
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Jun 9 09:10:29 2023 +0200
fortran: Fix ICE on pr96024.f90 on big-endian hosts [PR96024]
The pr96024.f90 testcase ICEs on big-endian hosts. The problem is
that length->val.integer is accessed after checking
length->expr_type == EXPR_CONSTANT, but it is a CHARACTER constant
which uses length->val.character union member instead and on big-endian
we end up reading constant 0x100000000 rather than some small number
on little-endian and if target doesn't have enough memory for 4 times
that (i.e. 16GB allocation), it ICEs.
2023-06-09 Jakub Jelinek <jakub@redhat.com>
PR fortran/96024
* primary.cc (gfc_convert_to_structure_constructor): Only do
constant string ctor length verification and truncation/padding
if constant length has INTEGER type.
(cherry picked from commit 4cf6e322adc19f927859e0a5edfa93cec4b8c844)
next prev parent reply other threads:[~2023-06-09 7:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 19:30 [Bug fortran/96024] New: [9/10/11 " gscfq@t-online.de
2020-07-01 20:11 ` [Bug fortran/96024] " dominiq at lps dot ens.fr
2020-07-01 21:30 ` kargl at gcc dot gnu.org
2020-07-01 21:30 ` kargl at gcc dot gnu.org
2020-07-02 6:42 ` rguenth at gcc dot gnu.org
2020-07-04 9:29 ` dominiq at lps dot ens.fr
2020-07-04 14:24 ` sgk at troutmask dot apl.washington.edu
2020-07-24 5:17 ` tkoenig at gcc dot gnu.org
2020-07-24 15:30 ` kargl at gcc dot gnu.org
2021-06-01 8:17 ` [Bug fortran/96024] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27 9:42 ` [Bug fortran/96024] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-02-21 20:46 ` anlauf at gcc dot gnu.org
2023-02-21 21:28 ` anlauf at gcc dot gnu.org
2023-02-22 17:56 ` cvs-commit at gcc dot gnu.org
2023-03-04 19:51 ` cvs-commit at gcc dot gnu.org
2023-03-05 19:35 ` cvs-commit at gcc dot gnu.org
2023-03-05 19:36 ` cvs-commit at gcc dot gnu.org
2023-03-05 19:38 ` anlauf at gcc dot gnu.org
2023-03-05 19:39 ` anlauf at gcc dot gnu.org
2023-06-08 8:51 ` jakub at gcc dot gnu.org
2023-06-08 9:42 ` anlauf at gcc dot gnu.org
2023-06-09 7:14 ` cvs-commit at gcc dot gnu.org
2023-06-09 7:21 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-09 7:58 ` cvs-commit at gcc dot gnu.org
2023-06-09 8:00 ` cvs-commit at gcc dot gnu.org
2023-06-09 8:01 ` cvs-commit at gcc dot gnu.org
2023-06-09 8:45 ` jakub 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-96024-4-JIQmzfgbdz@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: link
Be 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).