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/99368] ICE in build_function_decl, at fortran/trans-decl.c:2381 Date: Sat, 08 Jul 2023 17:13:36 +0000 [thread overview] Message-ID: <bug-99368-4-gF93lrsqSw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99368-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99368 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>: https://gcc.gnu.org/g:9a2eab6172a8067e2f63e0fa2bcd5b2190656303 commit r14-2397-g9a2eab6172a8067e2f63e0fa2bcd5b2190656303 Author: Paul Thomas <pault@gcc.gnu.org> Date: Sat Jul 8 18:13:23 2023 +0100 Fortran: Fix default type bugs in gfortran [PR99139, PR99368] 2023-07-08 Steve Kargl <sgk@troutmask.apl.washington.edu> gcc/fortran PR fortran/99139 PR fortran/99368 * match.cc (gfc_match_namelist): Check for host associated or defined types before applying default type. (gfc_match_select_rank): Apply default type to selector of unknown type if possible. * resolve.cc (resolve_fl_variable): Do not apply local default initialization to assumed rank entities. gcc/testsuite/ PR fortran/99139 * gfortran.dg/pr99139.f90 : New test PR fortran/99368 * gfortran.dg/pr99368.f90 : New test
prev parent reply other threads:[~2023-07-08 17:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-03 18:04 [Bug fortran/99368] New: " gscfq@t-online.de 2021-03-03 21:42 ` [Bug fortran/99368] " anlauf at gcc dot gnu.org 2021-08-01 17:04 ` kargl at gcc dot gnu.org 2023-05-29 21:48 ` kargl at gcc dot gnu.org 2023-05-29 21:58 ` kargl at gcc dot gnu.org 2023-07-08 17:13 ` cvs-commit at gcc dot gnu.org [this message]
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-99368-4-gF93lrsqSw@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).