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/34640] ICE when assigning item of a derived-component to a pointer Date: Thu, 03 Jan 2008 09:42:00 -0000 [thread overview] Message-ID: <20080103091430.16485.qmail@sourceware.org> (raw) In-Reply-To: <bug-34640-15407@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from burnus at gcc dot gnu dot org 2008-01-03 09:14 ------- Reduced test; has nothing to do with BIND(C). I am not 100% sure it is valid. (Actually, glancing at the code, I had said it is invalid). However, it gives no error/warning (or ICE) with other compilers such as NAG f95, g95, openf95, ifort, which implies that it is presumably valid. MODULE test IMPLICIT NONE TYPE :: my_type INTEGER :: value END TYPE CONTAINS SUBROUTINE get_values(values) INTEGER,POINTER :: values(:) TYPE(my_type),POINTER :: d(:) values => d(:)%value END SUBROUTINE END MODULE -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|32630 |32834 nThis| | GCC build triplet|20080102 (experimental) | |[trunk revision 131253] | GCC host triplet|i686-pc-linux-gnu | GCC target triplet|GNU Fortran (GCC) 4.3.0 | Summary|ICE with c_f_pointer |ICE when assigning item of a | |derived-component to a | |pointer http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34640
next prev parent reply other threads:[~2008-01-03 9:15 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-02 16:01 [Bug fortran/34640] New: ICE with c_f_pointer francois dot jacq at irsn dot fr 2008-01-02 16:52 ` [Bug fortran/34640] " rguenth at gcc dot gnu dot org 2008-01-03 9:11 ` burnus at gcc dot gnu dot org 2008-01-03 9:42 ` burnus at gcc dot gnu dot org [this message] 2008-01-03 15:38 ` [Bug fortran/34640] ICE when assigning item of a derived-component to a pointer pault at gcc dot gnu dot org 2008-01-03 18:08 ` pault at gcc dot gnu dot org 2008-03-14 13:25 ` pault at gcc dot gnu dot org 2008-10-05 20:27 ` pault at gcc dot gnu dot org 2008-11-06 6:26 ` pault at gcc dot gnu dot org 2008-11-06 6:27 ` pault at gcc dot gnu dot org 2008-12-11 16:14 ` burnus at gcc dot gnu dot org 2009-04-06 10:57 ` pault at gcc dot gnu dot org 2010-04-27 19:48 ` dfranke at gcc dot gnu dot org 2010-04-27 20:08 ` dominiq at lps dot ens dot fr 2010-05-18 22:22 ` dfranke at gcc dot gnu dot org 2010-05-18 22:28 ` dfranke at gcc dot gnu dot org 2010-05-18 22:30 ` dfranke at gcc dot gnu dot org [not found] <bug-34640-4@http.gcc.gnu.org/bugzilla/> 2010-11-25 20:44 ` jvdelisle at gcc dot gnu.org 2010-11-25 21:15 ` jvdelisle at gcc dot gnu.org 2010-12-28 22:31 ` dfranke at gcc dot gnu.org 2011-05-31 14:14 ` otte.martin at epa dot gov 2011-05-31 14:35 ` otte.martin at epa dot gov 2013-03-29 8:40 ` Joost.VandeVondele at mat dot ethz.ch 2013-03-29 10:31 ` Joost.VandeVondele at mat dot ethz.ch 2013-06-30 15:55 ` dominiq at lps dot ens.fr 2014-06-08 15:11 ` fxcoudert at gcc dot gnu.org 2014-06-08 15:36 ` fxcoudert 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=20080103091430.16485.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: 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).