public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107426] [12/13 Regression] ICE in gfc_compare_derived_types, at fortran/interface.cc:636
Date: Thu, 27 Oct 2022 00:22:23 +0000 [thread overview]
Message-ID: <bug-107426-4-LG9oVjzlqc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107426-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107426
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
I don't see this on x86_64-*-freebsd, but I also build with
--enable-checking=yes which may or may not mask issues. I'll note that running
valgrind on `f951 a.f90` yields a long listing which starts with
Error: END INTERFACE statement expected at (1)
==81746== Invalid read of size 8
==81746== at 0x899905: gfc_find_typebound_intrinsic_op(gfc_symbol*, bool*,
gfc_intrinsic_op, bool, locus*) (class.cc:3023)
==81746== by 0x8CDED8: matching_typebound_op(gfc_expr**,
gfc_actual_arglist*, gfc_intrinsic_op, char const*, char const**)
(interface.cc:4415)
==81746== by 0x8CE72C: gfc_extend_assign(gfc_code*, gfc_namespace*)
(interfac
probably not a good thing.
next prev parent reply other threads:[~2022-10-27 0:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 18:40 [Bug fortran/107426] New: " gscfq@t-online.de
2022-10-26 19:42 ` [Bug fortran/107426] " anlauf at gcc dot gnu.org
2022-10-27 0:22 ` kargl at gcc dot gnu.org [this message]
2022-10-28 11:35 ` rguenth at gcc dot gnu.org
2023-03-12 12:31 ` mikael at gcc dot gnu.org
2023-03-12 16:45 ` mikael at gcc dot gnu.org
2023-03-12 16:47 ` mikael at gcc dot gnu.org
2023-03-12 17:31 ` mikael at gcc dot gnu.org
2023-05-08 12:25 ` [Bug fortran/107426] [12/13/14 " rguenth at gcc dot gnu.org
2024-03-22 13:33 ` cvs-commit at gcc dot gnu.org
2024-03-30 9:13 ` pault at gcc dot gnu.org
2024-03-30 10:28 ` mikael at gcc dot gnu.org
2024-03-31 14:25 ` cvs-commit at gcc dot gnu.org
2024-04-02 13:08 ` cvs-commit at gcc dot gnu.org
2024-04-02 13:11 ` cvs-commit at gcc dot gnu.org
2024-04-02 13:13 ` mikael 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-107426-4-LG9oVjzlqc@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: link
Be 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).