public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51605] internal compiler error gfc_trans_block_construct, at fortran/trans-stmt.c:984
Date: Sun, 18 Dec 2011 16:57:00 -0000	[thread overview]
Message-ID: <bug-51605-4-FWTmSxuJx2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51605-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51605

--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-12-18 16:39:24 UTC ---
On Sun, Dec 18, 2011 at 10:01:13AM +0000, burnus at gcc dot gnu.org wrote:
> 
> Dan, Stave: If possible, please also update your GCC to 2011-12-11 or newer -
> at least if you use OOP/polymorphism features. (You might be able to get a
> newer binary from http://gcc.gnu.org/wiki/GFortranBinaries )
> 

I did the update last night whlie dreamed of sugarplums.
This morning with the new gfortran, I get the error messages
that you and Domonique report:

laptop:kargl[221] gfc4x -c coco.f90
coco.f90:91.24:

         integer_ptr => symbol_ptr
                        1
Error: Pointer assignment target is neither TARGET nor POINTER at (1)
coco.f90:94.24:

         logical_ptr => symbol_ptr
                        1
Error: Pointer assignment target is neither TARGET nor POINTER at (1)


  parent reply	other threads:[~2011-12-18 16:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 22:46 [Bug fortran/51605] New: " danlnagle at me dot com
2011-12-17 23:26 ` [Bug fortran/51605] " danlnagle at me dot com
2011-12-17 23:48 ` dominiq at lps dot ens.fr
2011-12-18  9:24 ` kargl at gcc dot gnu.org
2011-12-18 10:08 ` burnus at gcc dot gnu.org
2011-12-18 13:55 ` danlnagle at me dot com
2011-12-18 14:15 ` burnus at gcc dot gnu.org
2011-12-18 16:57 ` sgk at troutmask dot apl.washington.edu [this message]
2011-12-19 11:52 ` burnus at gcc dot gnu.org
2011-12-19 13:19 ` burnus at gcc dot gnu.org
2011-12-19 15:32 ` burnus at gcc dot gnu.org
2011-12-19 15:54 ` danlnagle at me dot com
2011-12-19 18:56 ` burnus at gcc dot gnu.org
2011-12-19 20:26 ` burnus at gcc dot gnu.org
2011-12-19 20:30 ` burnus at gcc dot gnu.org
2013-12-14 20:15 ` dominiq at lps dot ens.fr
2013-12-14 22:25 ` janus at gcc dot gnu.org
2023-03-06 17:18 ` anlauf 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-51605-4-FWTmSxuJx2@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: 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).