public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/57042] Strange typespec with -fdump-parse-tree Date: Wed, 29 Dec 2021 13:37:09 +0000 [thread overview] Message-ID: <bug-57042-4-HkFzP91Qle@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57042-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57042 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-valid-code |diagnostic CC| |fxcoudert at gcc dot gnu.org Version|4.9.0 |12.0 --- Comment #14 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- The bug in the parse tree dump is still present, as ADJUSTL and TRIM have unknown type: $ cat s.f90 program main implicit none print *, adjustl(" a ") print *, trim(" a ") end $ gfortran -fdump-fortran-original s.f90 Namespace: A-Z: (UNKNOWN 0) procedure name = main symtree: 'adjustl' || symbol: 'adjustl' type spec : (UNKNOWN 0) attributes: (PROCEDURE INTRINSIC-PROC FUNCTION ARRAY-OUTER-DEPENDENCY) result: adjustl symtree: 'main' || symbol: 'main' type spec : (UNKNOWN 0) attributes: (PROGRAM PUBLIC SUBROUTINE IS-MAIN-PROGRAM) symtree: 'trim' || symbol: 'trim' type spec : (UNKNOWN 0) attributes: (PROCEDURE INTRINSIC-PROC FUNCTION ARRAY-OUTER-DEPENDENCY) result: trim code: WRITE UNIT=6 FMT=-1 TRANSFER 'a ' DT_END WRITE UNIT=6 FMT=-1 TRANSFER ' a' DT_END ------------------------------------------
prev parent reply other threads:[~2021-12-29 13:37 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-23 10:09 [Bug fortran/57042] New: ICE/Segfault " burnus at gcc dot gnu.org 2013-05-01 18:49 ` [Bug fortran/57042] " tkoenig at gcc dot gnu.org 2013-05-01 18:54 ` dominiq at lps dot ens.fr 2013-05-01 19:08 ` [Bug fortran/57042] [4.7/4.8/4.9 Regression] " dominiq at lps dot ens.fr 2013-05-01 19:45 ` tkoenig at gcc dot gnu.org 2013-05-15 13:28 ` rguenth at gcc dot gnu.org 2013-12-31 14:58 ` [Bug fortran/57042] [4.7/4.8 " janus at gcc dot gnu.org 2013-12-31 15:05 ` janus at gcc dot gnu.org 2014-01-09 11:06 ` janus at gcc dot gnu.org 2014-01-11 11:54 ` janus at gcc dot gnu.org 2014-01-11 20:35 ` janus at gcc dot gnu.org 2014-01-11 22:48 ` janus at gcc dot gnu.org 2014-01-11 23:03 ` [Bug fortran/57042] " janus at gcc dot gnu.org 2014-06-12 13:53 ` rguenth at gcc dot gnu.org 2021-12-29 13:37 ` fxcoudert 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-57042-4-HkFzP91Qle@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).