public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38536] ICE with C_LOC in resolve.c due to not properly going through expr->ref Date: Sat, 22 Jan 2011 19:23:00 -0000 [thread overview] Message-ID: <bug-38536-4-LFjCST8QQl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-38536-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38536 --- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2011-01-22 17:30:27 UTC --- Author: tkoenig Date: Sat Jan 22 17:30:22 2011 New Revision: 169130 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169130 Log: 2011-01-22 Thomas Koenig <tkoenig@gcc.gnu.org> PR fortran/38536 * resolve.c (gfc_iso_c_func_interface): For C_LOC, check for array sections followed by component references which are illegal. Also check for coindexed arguments. 2011-01-22 Thomas Koenig <tkoenig@gcc.gnu.org> PR fortran/38536 * gfortran.dg/c_loc_tests_16.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/c_loc_tests_16.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-01-22 17:31 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-38536-4@http.gcc.gnu.org/bugzilla/> 2011-01-09 0:47 ` tkoenig at gcc dot gnu.org 2011-01-09 15:33 ` burnus at gcc dot gnu.org 2011-01-09 15:38 ` dominiq at lps dot ens.fr 2011-01-09 16:00 ` burnus at gcc dot gnu.org 2011-01-09 16:00 ` tkoenig at gcc dot gnu.org 2011-01-09 16:02 ` tkoenig at netcologne dot de 2011-01-13 20:02 ` tkoenig at gcc dot gnu.org 2011-01-14 9:59 ` burnus at gcc dot gnu.org 2011-01-14 19:53 ` tkoenig at gcc dot gnu.org 2011-01-22 19:23 ` tkoenig at gcc dot gnu.org [this message] 2011-01-25 16:26 ` burnus at gcc dot gnu.org 2012-08-26 9:14 ` mikael at gcc dot gnu.org 2013-03-25 15:54 ` burnus at gcc dot gnu.org 2013-03-25 17:56 ` burnus at gcc dot gnu.org 2008-12-15 20:34 [Bug fortran/38536] New: " burnus at gcc dot gnu dot org 2008-12-26 22:55 ` [Bug fortran/38536] " mikael at gcc dot gnu dot org 2008-12-26 23:06 ` mikael at gcc dot gnu dot org 2008-12-27 11:41 ` dominiq at lps dot ens dot fr 2008-12-27 13:02 ` dominiq at lps dot ens dot fr 2008-12-27 23:24 ` mikael at gcc dot gnu dot org 2008-12-30 22:48 ` mikael at gcc dot gnu dot org 2008-12-31 15:38 ` brtnfld at hdfgroup dot org 2009-01-04 12:27 ` dominiq at lps dot ens dot fr 2009-01-04 13:01 ` mikael at gcc dot gnu dot org 2010-05-02 15:09 ` dfranke at gcc dot gnu dot org 2010-05-03 14:50 ` brtnfld at hdfgroup dot 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-38536-4-LFjCST8QQl@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).