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/95091] ICE in gfc_hash_value, at fortran/class.c:538
Date: Thu, 11 Jun 2020 14:03:46 +0000 [thread overview]
Message-ID: <bug-95091-4-uo1eHTVkzB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95091-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95091
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:605e9b1a9b3250537a7269eba7e9c316b0f00d29
commit r10-8273-g605e9b1a9b3250537a7269eba7e9c316b0f00d29
Author: Harald Anlauf <anlauf@gmx.de>
Date: Sun Jun 7 16:43:12 2020 +0200
PR fortran/95091 - Buffer overflows with submodules and long symbols
Add cast to fix bootstrap error with -Werror=sign-compare.
gcc/fortran/
PR fortran/95091
* class.c (gfc_hash_value): Add cast.
(cherry picked from commit 5aaccde3db39fac7e7f6677ceccc1eadd9c6a424)
next prev parent reply other threads:[~2020-06-11 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:45 [Bug fortran/95091] New: " gscfq@t-online.de
2020-06-06 20:48 ` [Bug fortran/95091] " anlauf at gcc dot gnu.org
2020-06-06 21:13 ` anlauf at gcc dot gnu.org
2020-06-07 12:47 ` cvs-commit at gcc dot gnu.org
2020-06-07 14:43 ` cvs-commit at gcc dot gnu.org
2020-06-08 19:01 ` cvs-commit at gcc dot gnu.org
2020-06-11 14:03 ` cvs-commit at gcc dot gnu.org
2020-06-11 14:03 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-11 14:20 ` cvs-commit at gcc dot gnu.org
2020-06-11 14:20 ` cvs-commit at gcc dot gnu.org
2020-06-11 14:22 ` anlauf 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-95091-4-uo1eHTVkzB@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).