public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95304] New: Clean up some code for finalization
Date: Sun, 24 May 2020 12:01:52 +0000 [thread overview]
Message-ID: <bug-95304-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95304
Bug ID: 95304
Summary: Clean up some code for finalization
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
Just looked at the output of
gfortran -fdump-fortran-original finalize_28.f90
which has
symtree: 'idx2' || symbol: 'idx2'
type spec : (INTEGER 8)
attributes: (VARIABLE ARTIFICIAL)
symtree: 'ignore' || symbol: 'ignore'
type spec : (INTEGER 4)
attributes: (VARIABLE ARTIFICIAL)
symtree: 'is_contiguous'|| symbol: 'is_contiguous'
type spec : (LOGICAL 4)
attributes: (VARIABLE ARTIFICIAL)
symtree: 'nelem' || symbol: 'nelem'
[...]
DO __final_coo_graphs_Coo_graph:idx=1_8
__convert_i4_i8[[((_F.rank[[((__final_coo_graphs_Coo_graph:array(FULL)))]]))]]
1_8
ASSIGN
__final_coo_graphs_Coo_graph:strides(__final_coo_graphs_Coo_graph:idx)
_F.stride[[((__final_coo_graphs_Coo_graph:array(FULL))
(__final_coo_graphs_Coo_graph:idx))]]
ASSIGN
__final_coo_graphs_Coo_graph:sizes(__final_coo_graphs_Coo_graph:idx) (*
__final_coo_graphs_Coo_graph:sizes((- __final_coo_graphs_Coo_graph:idx 1_8))
_F.size[[((__final_coo_graphs_Coo_graph:array(FULL))
(__final_coo_graphs_Coo_graph:idx) (8_8))]])
IF (/=
__final_coo_graphs_Coo_graph:strides(__final_coo_graphs_Coo_graph:idx)
__final_coo_graphs_Coo_graph:sizes((- __final_coo_graphs_Coo_graph:idx 1_8)))
ASSIGN __final_coo_graphs_Coo_graph:is_contiguous .false.
ENDIF
END DO
We should be able to use the is_contiguous intrinsic and also
use variable names which are prefixed with __ so we can not collide
with user variables under any circumstances.
next reply other threads:[~2020-05-24 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 12:01 tkoenig at gcc dot gnu.org [this message]
2020-05-24 12:02 ` [Bug fortran/95304] " tkoenig at gcc dot gnu.org
2021-02-14 18:37 ` dominiq at lps dot ens.fr
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-95304-4@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).