public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/48776] New: ICE(segfault) after -std=f95 diagnostic error involving PROCEDURE Date: Tue, 26 Apr 2011 18:46:00 -0000 [thread overview] Message-ID: <bug-48776-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48776 Summary: ICE(segfault) after -std=f95 diagnostic error involving PROCEDURE Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: error-recovery, ice-on-invalid-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org Follow up to bug 48279 comment 7 and 48279 comment 11. The following program segfaults with -std=f95 after printing the diagnostic: procedure get1 1 Error: Fortran 2003: PROCEDURE statement at (1) f951: internal compiler error: Segmentation fault Valgrind shows tons of errors, starting with: ==22545== Invalid read of size 8 ==22545== at 0x52FD8C: resolve_symbol (resolve.c:10004) ==22545== by 0x54BA76: traverse_ns (symbol.c:3379) ==22545== by 0x53919B: resolve_types (resolve.c:13261) ==22545== by 0x52E3D3: gfc_resolve (resolve.c:13357) The testcase: interface get procedure get1 end interface integer :: h call set1 (get (h)) contains subroutine set1 (a) integer, intent(in) :: a end subroutine integer function get1 (s) integer :: s end function end
next reply other threads:[~2011-04-26 18:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-26 18:46 burnus at gcc dot gnu.org [this message] 2013-06-16 13:13 ` [Bug fortran/48776] " dominiq at lps dot ens.fr 2023-08-26 18:29 ` mikael at gcc dot gnu.org 2023-08-26 18:30 ` mikael at gcc dot gnu.org 2023-08-26 19:47 ` mikael at gcc dot gnu.org 2023-08-30 12:20 ` cvs-commit at gcc dot gnu.org 2023-08-30 19:38 ` mikael at gcc dot gnu.org 2023-08-30 19:39 ` mikael at gcc dot gnu.org 2024-01-20 15:50 ` cvs-commit 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-48776-4@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).