public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aserranot at aemet dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99651] New: Cannot change attributes of USE-associated intrinsic Date: Thu, 18 Mar 2021 17:49:58 +0000 [thread overview] Message-ID: <bug-99651-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99651 Bug ID: 99651 Summary: Cannot change attributes of USE-associated intrinsic Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: aserranot at aemet dot es Target Milestone: --- Created attachment 50424 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50424&action=edit Source files to reproduce the problem When I make a minimal example, the problem does not appear. So, I have taken my code and begun to simplify it while testing that, after each simplification, the problem remains. I use a fortran wrapper for the udunits by Michel Valin (Copyright Université du Québec à Montréal) and it seems that when I erase the corresponding use statement and all the variables of a type defined in the udunits2 wrapper, the problem disapears. So I think that the problem is triggered in some way by that module. I attach my code and the module. To compile, issue the following commands in a directory where you have the files f_udunits_2.f90, f_udunits_2.inc and gfortran_bug_example.f90: gfortran -J. -cpp -fno-realloc-lhs -fopenmp -fcheck=bounds -fcheck=all -g -O0 -Wall -c f_udunits_2.f90 gfortran -J. -cpp -fno-realloc-lhs -fopenmp -fcheck=bounds -fcheck=all -g -O0 -Wall -c gfortran_bug_example.f90 In my system, the output from the last command is: gfortran_bug_example.f90:41:53: 41 | type(typeNode), pointer :: Next => null() | 1 Error: No se pueden cambiar los atributos del símbolo asociado con USE null en (1) gfortran_bug_example.f90:45:45: 45 | type(typeNode), pointer :: Head => null() | 1 Error: No se pueden cambiar los atributos del símbolo asociado con USE null en (1) gfortran_bug_example.f90:46:45: 46 | type(typeNode), pointer :: Last => null() | 1 Error: No se pueden cambiar los atributos del símbolo asociado con USE null en (1) gfortran_bug_example.f90:62:30: 62 | class(typeFieldsList) :: FieldsList | 1 Error: Derived type ‘typefieldslist’ at (1) is being used before it is defined gfortran_bug_example.f90:66:30: 66 | class(typeFieldsList) :: Fields | 1 Error: Derived type ‘typefieldslist’ at (1) is being used before it is defined gfortran_bug_example.f90:67:25: 67 | class(typeField), intent(in) :: Field | 1 Error: Derived type ‘typefield’ at (1) is being used before it is defined gfortran_bug_example.f90:71:30: 71 | class(typeFieldsList), target :: Fields | 1 Error: Derived type ‘typefieldslist’ at (1) is being used before it is defined gfortran_bug_example.f90:73:25: 73 | class(typeField), pointer :: Ptr | 1 Error: Derived type ‘typefield’ at (1) is being used before it is defined
next reply other threads:[~2021-03-18 17:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-18 17:49 aserranot at aemet dot es [this message] 2021-03-18 20:16 ` [Bug fortran/99651] " burnus at gcc dot gnu.org 2021-03-18 20:16 ` burnus at gcc dot gnu.org 2021-03-18 20:25 ` burnus at gcc dot gnu.org 2021-03-19 8:51 ` burnus at gcc dot gnu.org 2021-03-26 7:40 ` cvs-commit at gcc dot gnu.org 2021-03-29 9:47 ` cvs-commit at gcc dot gnu.org 2021-05-03 13:20 ` burnus 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-99651-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: linkBe 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).