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/112407] [13/14 Regression] Fix for PR37336 triggers an ICE in gfc_format_decoder while constructing a vtab
Date: Tue, 02 Apr 2024 13:19:20 +0000	[thread overview]
Message-ID: <bug-112407-4-mpuJnMmq48@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112407-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112407

--- Comment #10 from GCC 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:35408b3669fac104cd380582b32e32c64a603d8b

commit r14-9752-g35408b3669fac104cd380582b32e32c64a603d8b
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Tue Apr 2 14:19:09 2024 +0100

    Fortran: Fix wrong recursive errors and class initialization [PR112407]

    2024-04-02  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/112407
            * resolve.cc (resolve_procedure_expression): Change the test for
            for recursion in the case of hidden procedures from modules.
            (resolve_typebound_static): Add warning for possible recursive
            calls to typebound procedures.
            * trans-expr.cc (gfc_trans_class_init_assign): Do not apply
            default initializer to class dummy where component initializers
            are all null.

    gcc/testsuite/
            PR fortran/112407
            * gfortran.dg/pr112407a.f90: New test.
            * gfortran.dg/pr112407b.f90: New test.

  parent reply	other threads:[~2024-04-02 13:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 15:26 [Bug fortran/112407] New: [13 " trnka at scm dot com
2023-11-06 15:27 ` [Bug fortran/112407] " trnka at scm dot com
2023-11-07  8:34 ` [Bug fortran/112407] [13/14 " rguenth at gcc dot gnu.org
2023-11-07 14:25 ` pault at gcc dot gnu.org
2023-11-07 16:04 ` trnka at scm dot com
2023-11-08 10:51 ` pault at gcc dot gnu.org
2023-11-08 15:32 ` trnka at scm dot com
2023-11-09 14:03 ` pault at gcc dot gnu.org
2024-03-29  7:57 ` pault at gcc dot gnu.org
2024-03-29 14:10 ` pault at gcc dot gnu.org
2024-03-30  7:27 ` pault at gcc dot gnu.org
2024-04-02 13:19 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-23  9:45 ` [Bug fortran/112407] [13 " pault at gcc dot gnu.org
2024-05-06  9:54 ` cvs-commit at gcc dot gnu.org
2024-05-06  9:55 ` pault at gcc dot gnu.org
2024-05-06  9:58 ` trnka at scm dot com

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-112407-4-mpuJnMmq48@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).