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/49961] type bounded function can not return a pointer of a array Date: Wed, 03 Aug 2011 15:21:00 -0000 [thread overview] Message-ID: <bug-49961-4-6eHNP6QYqp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49961-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49961 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-03 15:21:32 UTC --- Thanks for the report. As it is not a regression, I don't think the fix will be back-ported. Fortunately, it seems to be fixed in 4.6.x and in the current developer version 4.7. For using OOP programming features such as type-bound procedures and polymorphism, it is best to use GCC 4.6 or 4.7. See http://gcc.gnu.org/wiki/OOP for an overview of fixed and still unfixed OOP bugs by GCC version. Maybe Ubuntu also has a newer version, which can be installed besides (or instead of) the system GCC. If not, Debian has GCC 4.6.1 in Testing/Unstable, cf. http://packages.debian.org/search?keywords=gfortran&searchon=names&suite=all§ion=all Additionally, unofficial nightly builds of GCC are available from http://gcc.gnu.org/wiki/GFortranBinaries Those can also be installed without root permissions in some directory.
next prev parent reply other threads:[~2011-08-03 15:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-03 13:02 [Bug fortran/49961] New: " quaintchewster at gmail dot com 2011-08-03 13:18 ` [Bug fortran/49961] " dominiq at lps dot ens.fr 2011-08-03 15:21 ` burnus at gcc dot gnu.org [this message] 2011-08-04 17:25 ` [Bug fortran/49961] [OOP] type-bound " janus at gcc dot gnu.org 2011-08-04 17:46 ` janus at gcc dot gnu.org 2011-08-11 3:45 ` quaintchewster at gmail dot com 2011-08-15 10:41 ` janus 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-49961-4-6eHNP6QYqp@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).