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/64474] [4.8 Regression] transfer(c_null_ptr, ...) causes an internal error
Date: Fri, 02 Jan 2015 15:28:00 -0000	[thread overview]
Message-ID: <bug-64474-4-st52cGRBin@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64474-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64474

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-01-02
                 CC|                            |janus at gcc dot gnu.org
            Summary|transfer(c_null_ptr, ...)   |[4.8 Regression]
                   |causes an internal error    |transfer(c_null_ptr, ...)
                   |                            |causes an internal error
     Ever confirmed|0                           |1

--- Comment #1 from janus at gcc dot gnu.org ---
I see the ICE with 4.7.4 and 4.8.3, but it is gone with 4.9.1 and trunk.

Also there is no ICE in 4.6.4, which technically makes it a regression. If we
can identify the commit which fixed this in 4.9, it could be backported to 4.8.

Btw, 4.7 and earlier show the warning:

    subroutine croutine( array ) bind(c,name='croutine')
                              1
Warning: Variable 'array' at (1) is a parameter to the BIND(C) procedure
'croutine' but may not be C interoperable


  reply	other threads:[~2015-01-02 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 15:14 [Bug fortran/64474] New: " arjen.markus895 at gmail dot com
2015-01-02 15:28 ` janus at gcc dot gnu.org [this message]
2015-01-02 22:06 ` [Bug fortran/64474] [4.8 Regression] " arjen.markus895 at gmail dot com
2015-01-09 11:31 ` rguenth at gcc dot gnu.org
2015-01-23 19:25 ` dominiq at lps dot ens.fr
2015-02-11 14:31 ` 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-64474-4-st52cGRBin@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).