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/59104] Wrong result with SIZE specification expression
Date: Thu, 20 Jun 2024 07:01:55 +0000	[thread overview]
Message-ID: <bug-59104-4-J0IeIzWwAI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59104-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 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:ccaa39a268bef2a1d8880022696ff2dcaa6af941

commit r15-1468-gccaa39a268bef2a1d8880022696ff2dcaa6af941
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Thu Jun 20 08:01:36 2024 +0100

    Fortran: Auto array allocation with function dependencies [PR59104]

    2024-06-20  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/59104
            * dependency.cc (dependency_fcn, gfc_function_dependency): New
            functions to detect dependency in array bounds and character
            lengths on old style function results.
            * dependency.h : Add prototype for gfc_function_dependency.
            * error.cc (error_print): Remove trailing space.
            * gfortran.h : Remove dummy_order and add fn_result_spec.
            * symbol.cc : Remove declaration of next_dummy_order..
            (gfc_set_sym_referenced): remove setting of symbol dummy order.
            * trans-array.cc (gfc_trans_auto_array_allocation): Detect
            non-dummy symbols with function dependencies and put the
            allocation at the end of the initialization code.
            * trans-decl.cc : Include dependency.h.
            (decl_order): New function that determines uses the location
            field of the symbol 'declared_at' to determine the order of two
            declarations.
            (gfc_defer_symbol_init): Call gfc_function_dependency to put
            dependent symbols in the right part of the tlink chain. Use
            the location field of the symbol declared_at to determine the
            order of declarations.
            (gfc_trans_auto_character_variable): Put character length
            initialization of dependent symbols at the end of the chain.
            * trans.cc (gfc_add_init_cleanup): Add boolean argument with
            default false that determines whther an expression is placed at
            the back or the front of the initialization chain.
            * trans.h : Update the prototype for gfc_add_init_cleanup.

    gcc/testsuite/
            PR fortran/59104
            * gfortran.dg/dependent_decls_2.f90: New test.

      parent reply	other threads:[~2024-06-20  7:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13  7:33 [Bug fortran/59104] New: " burnus at gcc dot gnu.org
2013-12-19 11:31 ` [Bug fortran/59104] " dominiq at lps dot ens.fr
2015-08-18  8:15 ` fxcoudert at gcc dot gnu.org
2022-01-24 21:57 ` anlauf at gcc dot gnu.org
2024-05-22  7:46 ` pault at gcc dot gnu.org
2024-05-23  5:30 ` pault at gcc dot gnu.org
2024-06-04 21:51 ` pault at gcc dot gnu.org
2024-06-20  7:01 ` 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-59104-4-J0IeIzWwAI@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).