public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105167] ICE in gfc_set_default_type, at fortran/symbol.cc:298 Date: Tue, 05 Apr 2022 16:22:58 +0000 [thread overview] Message-ID: <bug-105167-4-RwfN1ol6SP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105167-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105167 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid, | |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- Interestingly, this type-spec "character(n)" with undefined "n" is simply ignored in following test case : $ cat z7.f90 program p print *, len([character(n) :: '']) print *, len([character(n) :: '1']) print *, len([character(n) :: '12']) print *, len([character(n) :: '123']) print *, len([character(n) :: '123456789']) print *, len([character(n) :: '1234567890123456789']) end $ gfortran-12-20220403 z7.f90 && ./a.out 0 1 2 3 9 19
next prev parent reply other threads:[~2022-04-05 16:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 16:22 [Bug fortran/105167] New: " gscfq@t-online.de 2022-04-05 16:22 ` gscfq@t-online.de [this message] 2022-04-05 18:19 ` [Bug fortran/105167] " kargl at gcc dot gnu.org 2022-04-05 18:20 ` kargl at gcc dot gnu.org 2023-02-13 21:39 ` anlauf at gcc dot gnu.org 2023-04-26 6:55 ` rguenth at gcc dot gnu.org 2023-07-27 9:22 ` rguenth at gcc dot gnu.org 2024-05-21 9:11 ` 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-105167-4-RwfN1ol6SP@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).