public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects
Date: Fri, 01 Oct 2010 17:42:00 -0000	[thread overview]
Message-ID: <20101001174200.IDysu0aYXnnapDpo4skRV_nYjlnOYzqhH38arJqh0kM@z> (raw)
In-Reply-To: <bug-45827-4@http.gcc.gnu.org/bugzilla/>

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

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #19 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2010-10-01 17:42:40 UTC ---
After applying this patch to get rid of the error in comment #18:

--- a/cpp.c
+++ b/cpp.c
@@ -510,10 +510,11 @@ gfc_cpp_post_options (void)
          || gfc_cpp_option.dump_includes))
     gfc_fatal_error("To enable preprocessing, use -cpp");

-  cpp_in = cpp_create_reader (CLK_GNUC89, NULL, line_table);
   if (!gfc_cpp_enabled ())
     return;

+  cpp_in = cpp_create_reader (CLK_GNUC89, NULL, line_table);
+
   gcc_assert (cpp_in);

   /* The cpp_options-structure defines far more flags than those set here.


I can now see this:

==7134== 4 bytes in 2 blocks are definitely lost in loss record 2 of 842
==7134==    at 0x4A04481: calloc (vg_replace_malloc.c:418)
==7134==    by 0xCCDB08: xcalloc (xmalloc.c:162)
==7134==    by 0x4F6E8F: parse_atom (module.c:1037)
==7134==    by 0x4FD7EC: gfc_use_module (module.c:5595)
==7134==    by 0x501C94: accept_statement (parse.c:1574)
==7134==    by 0x504A2A: parse_spec (parse.c:2588)
==7134==    by 0x5074F0: gfc_parse_file (parse.c:4109)
==7134==    by 0x53EB97: gfc_be_parse_file (f95-lang.c:242)
==7134==    by 0x83523F: toplev_main (toplev.c:955)
==7134==    by 0x3E9F21EC5C: (below main) (libc-start.c:226)
==7134== 
==7134== 159 bytes in 1 blocks are definitely lost in loss record 499 of 842
==7134==    at 0x4A04481: calloc (vg_replace_malloc.c:418)
==7134==    by 0xCCDB08: xcalloc (xmalloc.c:162)
==7134==    by 0x659E64: init_emit (emit-rtl.c:5574)
==7134==    by 0x6E3328: prepare_function_start (function.c:4382)
==7134==    by 0x6E8E88: init_function_start (function.c:4436)
==7134==    by 0x5554D6: trans_function_start.isra.2 (trans-decl.c:2002)
==7134==    by 0x55F7C0: gfc_generate_function_code (trans-decl.c:4557)
==7134==    by 0x543B8A: gfc_generate_module_code (trans.c:1433)
==7134==    by 0x507AD5: gfc_parse_file (parse.c:4377)
==7134==    by 0x53EB97: gfc_be_parse_file (f95-lang.c:242)
==7134==    by 0x83523F: toplev_main (toplev.c:955)
==7134==    by 0x3E9F21EC5C: (below main) (libc-start.c:226)
==7134== 
==7134== 184 bytes in 1 blocks are definitely lost in loss record 514 of 842
==7134==    at 0x4A04481: calloc (vg_replace_malloc.c:418)
==7134==    by 0xCCDB08: xcalloc (xmalloc.c:162)
==7134==    by 0x4C853F: gfc_get_expr (expr.c:48)
==7134==    by 0x51A924: extract_compcall_passed_object (resolve.c:5283)
==7134==    by 0x51A978: check_typebound_baseobject (resolve.c:5405)
==7134==    by 0x51AE09: resolve_typebound_call (resolve.c:5607)
==7134==    by 0x51E730: resolve_code (resolve.c:5843)
==7134==    by 0x51F1AB: gfc_resolve_blocks (resolve.c:8568)
==7134==    by 0x51D3E3: resolve_code (resolve.c:8810)
==7134==    by 0x51F332: resolve_codes (resolve.c:13323)
==7134==    by 0x51F23F: resolve_codes (resolve.c:13309)
==7134==    by 0x51171B: gfc_resolve (resolve.c:13350)
==7134== 
==7134== 192 (96 direct, 96 indirect) bytes in 6 blocks are definitely lost in
loss record 518 of 842
==7134==    at 0x4A04481: calloc (vg_replace_malloc.c:418)
==7134==    by 0xCCDB08: xcalloc (xmalloc.c:162)
==7134==    by 0x4F7C87: mio_formal_arglist (module.c:2517)
==7134==    by 0x4FA0CF: mio_component (module.c:2402)
==7134==    by 0x4FA49D: mio_symbol (module.c:2434)
==7134==    by 0x4FA7CF: load_needed (module.c:4171)
==7134==    by 0x4FA775: load_needed (module.c:4132)
==7134==    by 0x4FA780: load_needed (module.c:4133)
==7134==    by 0x4FA775: load_needed (module.c:4132)
==7134==    by 0x4FA775: load_needed (module.c:4132)
==7134==    by 0x4FA780: load_needed (module.c:4133)
==7134==    by 0x4FA775: load_needed (module.c:4132)
==7134== 


and several other similar messages.


  parent reply	other threads:[~2010-10-01 17:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 11:49 [Bug fortran/45827] New: " boschmann at tp1 dot physik.uni-siegen.de
2010-09-29 12:37 ` [Bug fortran/45827] " Joost.VandeVondele at pci dot uzh.ch
2010-09-29 12:44 ` [Bug fortran/45827] [4.6 Regression] ice in create_int_parameter_array Joost.VandeVondele at pci dot uzh.ch
2010-09-29 12:49 ` burnus at gcc dot gnu.org
2010-09-29 12:54 ` Joost.VandeVondele at pci dot uzh.ch
2010-09-29 13:02 ` mikael at gcc dot gnu.org
2010-09-29 13:18 ` Joost.VandeVondele at pci dot uzh.ch
2010-09-29 14:22 ` [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects mikael at gcc dot gnu.org
2010-09-29 14:30 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-29 14:30 ` mikael at gcc dot gnu.org
2010-09-29 14:59 ` mikael at gcc dot gnu.org
2010-09-30 10:19 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-30 10:44 ` burnus at gcc dot gnu.org
2010-09-30 17:47 ` boschmann at tp1 dot physik.uni-siegen.de
2010-09-30 18:39 ` burnus at gcc dot gnu.org
2010-10-01  6:52 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-01  7:57 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-01  8:13 ` burnus at gcc dot gnu.org
2010-10-01 14:39 ` jvdelisle at gcc dot gnu.org
     [not found] ` <20101001143948.D63711C0008C@msfrf2419.sfr.fr>
2010-10-01 15:17   ` Mikael Morin
2010-10-01 17:42 ` jvdelisle at gcc dot gnu.org [this message]
2010-10-21 12:28 ` janus at gcc dot gnu.org
2010-10-21 14:04 ` burnus at gcc dot gnu.org
2010-10-24 10:17 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-24 11:10 ` burnus at gcc dot gnu.org
2010-10-24 11:56 ` mikael at gcc dot gnu.org
2010-10-24 12:02 ` mikael at gcc dot gnu.org
2010-10-24 15:15 ` jvdelisle at gcc dot gnu.org
2010-10-24 15:48 ` mikael at gcc dot gnu.org
2010-10-24 18:57 ` jvdelisle at gcc dot gnu.org
2010-10-24 19:59 ` mikael at gcc dot gnu.org
2010-10-26 15:27 ` boschmann at tp1 dot physik.uni-siegen.de
2010-10-27  9:35 ` boschmann at tp1 dot physik.uni-siegen.de
2010-12-27  2:23 ` dfranke at gcc dot gnu.org
2010-12-27 14:22 ` [Bug fortran/45827] [4.6 Regression] mio_component_ref(): Component not found janus at gcc dot gnu.org
2010-12-27 14:27 ` dfranke at gcc dot gnu.org
2010-12-27 15:37 ` [Bug fortran/45827] [4.6 Regression] [OOP] " janus at gcc dot gnu.org
2010-12-27 22:18 ` dfranke at gcc dot gnu.org
2010-12-28  8:15 ` janus at gcc dot gnu.org
2010-12-28 12:23 ` dfranke at gcc dot gnu.org
2010-12-28 13:19 ` janus at gcc dot gnu.org
2010-12-28 17:27 ` dfranke at gcc dot gnu.org
2010-12-28 18:53 ` janus at gcc dot gnu.org
2010-12-28 21:22 ` janus at gcc dot gnu.org
2010-12-31 11:21 ` jakub at gcc dot gnu.org
2011-01-02 21:28 ` janus at gcc dot gnu.org
2011-01-03 12:56 ` boschmann at tp1 dot physik.uni-siegen.de
2011-01-03 13:14 ` janus 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=20101001174200.IDysu0aYXnnapDpo4skRV_nYjlnOYzqhH38arJqh0kM@z \
    --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).