public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46262] [4.6 Regression] [OOP] tree check: expected function_type or method_type, have pointer_type
Date: Tue, 02 Nov 2010 07:29:00 -0000 [thread overview]
Message-ID: <20101102072900.VZSseODDaUCXq0mK85O1eG0MRt7ipY6UUeRozk5UBFI@z> (raw)
In-Reply-To: <bug-46262-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46262
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #6 from janus at gcc dot gnu.org 2010-11-02 07:29:20 UTC ---
(In reply to comment #5)
> Passes at r162312 and fails at r162313.
Thanks for checking, Jerry. r162313 was Paul's fix for PR42385 ("poylmorphic
operators do not work"):
http://gcc.gnu.org/viewcvs?view=revision&revision=162313
next prev parent reply other threads:[~2010-11-02 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 19:35 [Bug fortran/46262] New: " janus at gcc dot gnu.org
2010-11-01 19:43 ` [Bug fortran/46262] " janus at gcc dot gnu.org
2010-11-01 19:45 ` janus at gcc dot gnu.org
2010-11-01 19:49 ` janus at gcc dot gnu.org
2010-11-02 3:33 ` jvdelisle at gcc dot gnu.org
2010-11-02 5:22 ` jvdelisle at gcc dot gnu.org
2010-11-02 7:29 ` janus at gcc dot gnu.org [this message]
2010-11-03 15:38 ` rguenth at gcc dot gnu.org
2010-11-03 16:02 ` jakub at gcc dot gnu.org
2010-11-28 15:48 ` jvdelisle at gcc dot gnu.org
2010-11-28 16:10 ` jvdelisle at gcc dot gnu.org
2011-01-05 9:35 ` [Bug fortran/46262] " janus at gcc dot gnu.org
2011-03-07 8:39 ` janus at gcc dot gnu.org
2011-03-22 14:54 ` janus at gcc dot gnu.org
2011-03-25 21:02 ` jakub at gcc dot gnu.org
2011-04-28 17:21 ` rguenth at gcc dot gnu.org
2012-01-02 12:48 ` pault at gcc dot gnu.org
2012-01-02 13:04 ` pault 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=20101102072900.VZSseODDaUCXq0mK85O1eG0MRt7ipY6UUeRozk5UBFI@z \
--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).