public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/93814] [11/12/13/14/15 Regression] ICE in build_entry_thunks, at fortran/trans-decl.c:2898 Date: Sat, 27 Apr 2024 15:22:24 +0000 [thread overview] Message-ID: <bug-93814-4-OMUTdOOvpn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93814-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93814 --- Comment #12 from David Binderman <dcb314 at hotmail dot com> --- Bit more detail: ./Lower/HLFIR/bindc-entry-stmt.f90:5:0: 5 | function foo() bind(c) Warning: Variable ‘foo’ at (1) may not be a C interoperable kind but it is BIND(C) [-Wc-binding-type] ./Lower/HLFIR/bindc-entry-stmt.f90:39:28: 39 | character(1) :: foo2, bar2 | 1 Warning: Variable ‘bar2’ at (1) may not be a C interoperable kind but it is BIND(C) [-Wc-binding-type] ==1442522== Invalid read of size 8 ==1442522== at 0x862E5E: quick_push (vec.h:1043) ==1442522== by 0x862E5E: vec_safe_push<tree_node*, va_gc> (vec.h:835) ==1442522== by 0x862E5E: build_entry_thunks (trans-decl.cc:3002) ==1442522== by 0x862E5E: gfc_create_function_decl(gfc_namespace*, bool) (trans-decl.cc:3157)
prev parent reply other threads:[~2024-04-27 15:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93814-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:58 ` [Bug fortran/93814] [9/10 " jakub at gcc dot gnu.org 2020-06-02 6:57 ` [Bug fortran/93814] [9/10/11 " markeggleston at gcc dot gnu.org 2020-06-03 15:40 ` gscfq@t-online.de 2021-06-01 8:16 ` [Bug fortran/93814] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug fortran/93814] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:39 ` jakub at gcc dot gnu.org 2023-07-07 10:36 ` [Bug fortran/93814] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-13 10:05 ` dcb314 at hotmail dot com 2024-04-27 15:22 ` dcb314 at hotmail dot com [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-93814-4-OMUTdOOvpn@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).