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/52469] [4.6/4.7/4.8 Regression] -fwhole-file bug: Wrong backend_decl for result of PPC function Date: Sat, 10 Mar 2012 09:21:00 -0000 [thread overview] Message-ID: <bug-52469-4-hepav1lv9J@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52469-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52469 --- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-03-10 09:20:27 UTC --- Author: burnus Date: Sat Mar 10 09:20:22 2012 New Revision: 185173 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=185173 Log: 2012-03-10 Tobias Burnus <burnus@net-b.de> PR fortran/52469 * trans-types.c (gfc_get_function_type): Handle backend_decl of a procedure pointer. 2012-03-10 Tobias Burnus <burnus@net-b.de> PR fortran/52469 * gfortran.dg/proc_ptr_34.f90: New. Added: branches/gcc-4_6-branch/gcc/testsuite/gfortran.dg/proc_ptr_34.f90 Modified: branches/gcc-4_6-branch/gcc/fortran/ChangeLog branches/gcc-4_6-branch/gcc/fortran/trans-types.c branches/gcc-4_6-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-03-10 9:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-03 16:32 [Bug fortran/52469] New: Defining function pointer interface palott at gmail dot com 2012-03-03 16:35 ` [Bug fortran/52469] " palott at gmail dot com 2012-03-04 22:38 ` [Bug fortran/52469] [4.6/4.7/4.8 Regression] " dominiq at lps dot ens.fr 2012-03-05 8:19 ` [Bug fortran/52469] [4.6/4.7/4.8 Regression] -fwhole-file bug: Wrong backend_decl for result of PPC function burnus at gcc dot gnu.org 2012-03-05 20:32 ` burnus at gcc dot gnu.org 2012-03-08 11:33 ` burnus at gcc dot gnu.org 2012-03-08 19:37 ` burnus at gcc dot gnu.org 2012-03-10 8:19 ` burnus at gcc dot gnu.org 2012-03-10 9:21 ` burnus at gcc dot gnu.org [this message] 2012-03-10 9:22 ` burnus 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-52469-4-hepav1lv9J@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).