public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42769] [OOP] ICE in resolve_typebound_procedure Date: Tue, 08 Jan 2013 19:43:00 -0000 [thread overview] Message-ID: <bug-42769-4-bnvjiRmHpM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-42769-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42769 --- Comment #37 from Mikael Morin <mikael at gcc dot gnu.org> 2013-01-08 19:42:47 UTC --- Author: mikael Date: Tue Jan 8 19:42:38 2013 New Revision: 195031 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195031 Log: PR fortran/42769 PR fortran/45836 PR fortran/45900 * module.c (read_module): Don't reuse local symtree if the associated symbol isn't exactly the one wanted. Don't reuse local symtree if it is ambiguous. * resolve.c (resolve_call): Use symtree's name instead of symbol's to lookup the symtree. PR fortran/42769 PR fortran/45836 PR fortran/45900 * gfortran.dg/use_23.f90: New test. * gfortran.dg/use_24.f90: New test. * gfortran.dg/use_25.f90: New test. * gfortran.dg/use_26.f90: New test. * gfortran.dg/use_27.f90: New test. Added: branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/use_23.f90 branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/use_24.f90 branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/use_25.f90 branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/use_26.f90 branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/use_27.f90 Modified: branches/gcc-4_7-branch/gcc/fortran/ChangeLog branches/gcc-4_7-branch/gcc/fortran/module.c branches/gcc-4_7-branch/gcc/fortran/resolve.c branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-01-08 19:43 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-42769-4@http.gcc.gnu.org/bugzilla/> 2011-02-23 23:36 ` mikael at gcc dot gnu.org 2011-02-24 22:07 ` mikael at gcc dot gnu.org 2011-02-25 0:55 ` mikael at gcc dot gnu.org 2011-03-01 16:27 ` mikael at gcc dot gnu.org 2011-03-25 20:08 ` jakub at gcc dot gnu.org 2011-04-28 16:51 ` rguenth at gcc dot gnu.org 2013-01-06 15:50 ` mikael at gcc dot gnu.org 2013-01-08 19:43 ` mikael at gcc dot gnu.org [this message] 2013-01-08 20:02 ` mikael at gcc dot gnu.org 2013-01-09 14:29 ` mikael at gcc dot gnu.org 2010-01-16 17:00 [Bug fortran/42769] New: " sfilippone at uniroma2 dot it 2010-05-14 11:53 ` [Bug fortran/42769] [OOP] " janus at gcc dot gnu dot org 2010-06-11 21:33 ` janus at gcc dot gnu dot org 2010-06-11 22:16 ` janus at gcc dot gnu dot org 2010-08-13 17:29 ` janus at gcc dot gnu dot org 2010-08-23 13:26 ` janus at gcc dot gnu dot org 2010-08-23 13:33 ` janus at gcc dot gnu dot org 2010-08-29 21:30 ` janus at gcc dot gnu dot org 2010-08-29 21:36 ` janus at gcc dot gnu dot 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-42769-4-bnvjiRmHpM@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).