public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44596] [OOP] Dynamic dispatch uses broken types
Date: Tue, 13 Jul 2010 10:01:00 -0000 [thread overview]
Message-ID: <20100713100105.19791.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44596-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #21 from burnus at gcc dot gnu dot org 2010-07-13 10:01 -------
(In reply to comment #19)
> > Paul, thanks for the check in. Do you plan to backport it to 4.5, which
> > sems to use the same code?
>
> Yes, I could do that on Thursday, when I am back in Barcelona. I do
> not have 4.5 on the laptop.
[...]
> When I add the vtype attribute and the above patch, almost every OOP test
> fails
Well, if it does not want to be fixed then we don't fix it. I had hoped that it
would be trivial - which turned out to be not the case.
OOP was announced as experimental (in 4.5) - thus, OOP users can easily jump
directly to 4.6.
> I think that, since we do not need this (yet!)
Then close it as FIXED (on the 4.6 trunk).
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44596
prev parent reply other threads:[~2010-07-13 10:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 19:08 [Bug fortran/44596] New: " rguenth at gcc dot gnu dot org
2010-06-19 19:16 ` [Bug fortran/44596] " rguenth at gcc dot gnu dot org
2010-06-22 15:01 ` [Bug fortran/44596] [OOP] " burnus at gcc dot gnu dot org
2010-06-22 19:15 ` paul dot richard dot thomas at gmail dot com
2010-06-23 17:36 ` paul dot richard dot thomas at gmail dot com
2010-07-01 14:22 ` rguenth at gcc dot gnu dot org
2010-07-01 14:22 ` rguenth at gcc dot gnu dot org
2010-07-01 14:25 ` dominiq at lps dot ens dot fr
2010-07-01 14:34 ` rguenth at gcc dot gnu dot org
2010-07-01 15:58 ` dominiq at lps dot ens dot fr
2010-07-01 18:27 ` pault at gcc dot gnu dot org
2010-07-04 14:41 ` pault at gcc dot gnu dot org
2010-07-05 12:32 ` rguenth at gcc dot gnu dot org
2010-07-05 13:14 ` burnus at gcc dot gnu dot org
2010-07-05 13:52 ` paul dot richard dot thomas at gmail dot com
2010-07-05 14:06 ` rguenther at suse dot de
2010-07-05 15:47 ` paul dot richard dot thomas at gmail dot com
2010-07-05 19:26 ` pault at gcc dot gnu dot org
2010-07-06 15:20 ` burnus at gcc dot gnu dot org
2010-07-06 15:28 ` paul dot richard dot thomas at gmail dot com
2010-07-11 17:45 ` pault at gcc dot gnu dot org
2010-07-13 10:01 ` burnus at gcc dot gnu dot org [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=20100713100105.19791.qmail@sourceware.org \
--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).