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/100027] ICE on storage_size with polymorphic argument
Date: Sun, 12 May 2024 05:59:59 +0000	[thread overview]
Message-ID: <bug-100027-4-rzffWJDvJ0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100027-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:b9294757f82aae8de6d98c122cd4e3b98f685217

commit r15-386-gb9294757f82aae8de6d98c122cd4e3b98f685217
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Sun May 12 06:59:45 2024 +0100

    Fortran: Unlimited polymorphic intrinsic function arguments [PR84006]

    2024-05-12  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/84006
            PR fortran/100027
            PR fortran/98534
            * iresolve.cc (gfc_resolve_transfer): Emit a TODO error for
            unlimited polymorphic mold.
            * trans-expr.cc (gfc_resize_class_size_with_len): Use the fold
            even if a block is not available in which to fix the result.
            (trans_class_assignment): Enable correct assignment of
            character expressions to unlimited polymorphic variables using
            lhs _len field and rse string_length.
            * trans-intrinsic.cc (gfc_conv_intrinsic_storage_size): Extract
            the class expression so that the unlimited polymorphic class
            expression can be used in gfc_resize_class_size_with_len to
            obtain the storage size for character payloads. Guard the use
            of GFC_DECL_SAVED_DESCRIPTOR by testing for DECL_LANG_SPECIFIC
            to prevent the ICE. Also, invert the order to use the class
            expression extracted from the argument.
            (gfc_conv_intrinsic_transfer): In same way as 'storage_size',
            use the _len field to obtaining the correct length for arg 1.
            Add a branch for the element size in bytes of class expressions
            with provision to make use of the unlimited polymorphic _len
            field. Again, the class references are explicitly identified.
            'mold_expr' was already declared. Use it instead of 'arg'. Do
            not fix 'dest_word_len' for deferred character sources because
            reallocation on assign makes use of it before it is assigned.

    gcc/testsuite/
            PR fortran/84006
            PR fortran/100027
            * gfortran.dg/storage_size_7.f90: New test.

            PR fortran/98534
            * gfortran.dg/transfer_class_4.f90: New test.

  parent reply	other threads:[~2024-05-12  6:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11  0:16 [Bug fortran/100027] New: " jrfsousa at gmail dot com
2021-04-11  0:37 ` [Bug fortran/100027] " jrfsousa at gmail dot com
2021-04-14 18:25 ` dominiq at lps dot ens.fr
2021-04-17 10:17 ` pault at gcc dot gnu.org
2024-05-12  5:59 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-12  6:06 ` pault 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-100027-4-rzffWJDvJ0@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).