public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114825] [11/12/13/14 Regression] Compiler error using gfortran and OpenMP since r5-1190 Date: Tue, 23 Apr 2024 15:18:45 +0000 [thread overview] Message-ID: <bug-114825-4-Gq07jMKVHk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114825-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114825 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yes, and the reason for that is that while in subroutine pr114825(b) type t real, allocatable :: m(:) end type t type(t), allocatable, target :: b(:) type(t), pointer :: d !$omp parallel private(d) d => b(1) !$omp end parallel contains subroutine sub ! d => b(1) end subroutine sub end subroutine pr114825 the d in the private clause is the VAR_DECL created by the Fortran FE with DECL_LANG_SPECIFIC, d in the private clause in the testcase without the d => b(1) commented out is a VAR_DECL created by tree-nested.cc: #5 0x000000000123a64b in build_decl (loc=21312, code=VAR_DECL, name=<identifier_node 0x7fffe9efc118 d>, type=<pointer_type 0x7fffe9f03150>) at ../../gcc/tree.cc:5379 #6 0x0000000000f4f39e in get_local_debug_decl (info=0x3b871d0, decl=<var_decl 0x7fffea137c60 d>, field=<field_decl 0x7fffe9f00720 d>) at ../../gcc/tree-nested.cc:1895 #7 0x0000000000f504c9 in convert_local_omp_clauses (pclauses=0x7fffea134780, wi=0x7fffffffd9b0) at ../../gcc/tree-nested.cc:2157 Perhaps get_local_debug_decl should also copy DECL_LANG_SPECIFIC? Of course, perhaps it might need e.g. DECL_LANG_FLAG_* too. If decl in there is just a VAR_DECL, we might as well just copy_node it and tweak afterwards, but if it is e.g. a PARM_DECL, that wouldn't be possible.
next prev parent reply other threads:[~2024-04-23 15:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-23 13:33 [Bug libgomp/114825] New: Compiler error using gfortran and OpenMP marcos.vanella at nist dot gov 2024-04-23 14:10 ` [Bug fortran/114825] [11/12/13/14 Regression] Compiler error using gfortran and OpenMP since r5-1190 jakub at gcc dot gnu.org 2024-04-23 14:57 ` burnus at gcc dot gnu.org 2024-04-23 15:18 ` jakub at gcc dot gnu.org [this message] 2024-04-24 16:27 ` jakub at gcc dot gnu.org 2024-04-25 18:15 ` cvs-commit at gcc dot gnu.org 2024-04-25 18:23 ` [Bug fortran/114825] [11/12/13 " jakub at gcc dot gnu.org 2024-05-09 4:26 ` cvs-commit at gcc dot gnu.org 2024-05-09 8:17 ` [Bug fortran/114825] [11/12 " jakub 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-114825-4-Gq07jMKVHk@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).