public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99169] [9/10/11 Regression] Segfault when passing allocatable scalar into intent(out) dummy argument
Date: Fri, 19 Feb 2021 20:13:21 +0000	[thread overview]
Message-ID: <bug-99169-4-FUls6Sk0i2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99169-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from anlauf at gcc dot gnu.org ---
A conservative solution simply disables the clobber:

diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c
index 103cb31c664..ce7bfaa89e8 100644
--- a/gcc/fortran/trans-expr.c
+++ b/gcc/fortran/trans-expr.c
@@ -6082,6 +6084,7 @@ gfc_conv_procedure_call (gfc_se * se, gfc_symbol * sym,
                        /* FIXME - PR 87395 and PR 41453  */
                        && e->symtree->n.sym->attr.save == SAVE_NONE
                        && !e->symtree->n.sym->attr.associate_var
+                       && !e->symtree->n.sym->attr.allocatable
                        && e->ts.type != BT_CHARACTER && e->ts.type !=
BT_DERIVED
                        && e->ts.type != BT_CLASS && !sym->attr.elemental;

This should result only in a missed optimization.
Is there a way to get sth. like:

  *i = {CLOBBER};

so that we do not clobber the pointer but the pointer to?

  parent reply	other threads:[~2021-02-19 20:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 17:31 [Bug fortran/99169] New: " townsend at astro dot wisc.edu
2021-02-19 19:49 ` [Bug fortran/99169] [9/10/11 Regression] " anlauf at gcc dot gnu.org
2021-02-19 19:58 ` anlauf at gcc dot gnu.org
2021-02-19 20:13 ` anlauf at gcc dot gnu.org [this message]
2021-02-19 20:20 ` anlauf at gcc dot gnu.org
2021-02-19 21:17 ` anlauf at gcc dot gnu.org
2021-02-21 20:44 ` cvs-commit at gcc dot gnu.org
2021-02-23 18:14 ` cvs-commit at gcc dot gnu.org
2021-02-23 18:27 ` cvs-commit at gcc dot gnu.org
2021-02-23 18:29 ` anlauf at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit 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-99169-4-FUls6Sk0i2@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).