public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/34828] ICE: GNU MP: Cannot reallocate memory for gfortran.dg/parameter_array_init_3.f90 Date: Mon, 26 May 2008 17:05:00 -0000 [thread overview] Message-ID: <20080526170507.29100.qmail@sourceware.org> (raw) In-Reply-To: <bug-34828-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #17 from jvdelisle at gcc dot gnu dot org 2008-05-26 17:05 ------- With the test case in comment#16 on x86-64-linux-gnu, I see this: ==11143== 416 bytes in 52 blocks are definitely lost in loss record 5 of 14 ==11143== at 0x4A059F6: malloc (vg_replace_malloc.c:149) ==11143== by 0x3FDCC07EF8: __gmp_default_allocate (in /usr/lib64/libgmp.so.3.4.2) ==11143== by 0x3FDCC18050: __gmpz_init_set (in /usr/lib64/libgmp.so.3.4.2) ==11143== by 0x4232A7: gfc_copy_shape (expr.c:338) ==11143== by 0x42331D: gfc_copy_expr (expr.c:515) ==11143== by 0x425266: simplify_parameter_variable (expr.c:1526) ==11143== by 0x425003: gfc_simplify_expr (expr.c:1641) ==11143== by 0x409F2F: expand_constructor (array.c:1437) ==11143== by 0x40A063: gfc_get_array_element (array.c:1791) ==11143== by 0x40B2FE: gfc_expand_constructor (array.c:1462) ==11143== by 0x45DBC9: gfc_resolve_expr (resolve.c:4337) ==11143== by 0x40B1CA: gfc_resolve_array_constructor (array.c:1572) ==11143== ==11143== ==11143== 632 bytes in 4 blocks are definitely lost in loss record 6 of 14 ==11143== at 0x4A04D1F: calloc (vg_replace_malloc.c:279) ==11143== by 0xB4304A: xcalloc (xmalloc.c:162) ==11143== by 0x55B877: init_emit (emit-rtl.c:5012) ==11143== by 0x5F3E62: prepare_function_start (function.c:3906) ==11143== by 0x5F5E98: init_function_start (function.c:3953) ==11143== by 0x492BDD: trans_function_start (trans-decl.c:1618) ==11143== by 0x499D6D: gfc_generate_function_code (trans-decl.c:3218) ==11143== by 0x45570B: gfc_parse_file (parse.c:3585) ==11143== by 0x47D81D: gfc_be_parse_file (f95-lang.c:258) ==11143== by 0x6E49F1: toplev_main (toplev.c:965) ==11143== by 0x3FF061E073: (below main) (libc-start.c:220) ==11143== ==11143== ==11143== 1,224 bytes in 9 blocks are definitely lost in loss record 8 of 14 ==11143== at 0x4A059F6: malloc (vg_replace_malloc.c:149) ==11143== by 0xB4300B: xrealloc (xmalloc.c:177) ==11143== by 0x8CAC80: vec_heap_o_reserve_1 (vec.c:176) ==11143== by 0x50609D: insn_locators_alloc (vecprim.h:27) ==11143== by 0xA9C778: tree_expand_cfg (cfgexpand.c:1850) ==11143== by 0x6686D6: execute_one_pass (passes.c:1284) ==11143== by 0x6688D0: execute_pass_list (passes.c:1334) ==11143== by 0x74A705: tree_rest_of_compilation (tree-optimize.c:421) ==11143== by 0x8FA841: cgraph_expand_function (cgraphunit.c:1148) ==11143== by 0x8FC5E3: cgraph_assemble_pending_functions (cgraphunit.c:514) ==11143== by 0x8FBB34: cgraph_finalize_function (cgraphunit.c:632) ==11143== by 0x49AFF5: gfc_generate_function_code (trans-decl.c:3481) ==11143== ==11143== ==11143== 62,028 (26,528 direct, 35,500 indirect) bytes in 348 blocks are definitely lost in loss record 12 of 14 ==11143== at 0x4A059F6: malloc (vg_replace_malloc.c:149) ==11143== by 0xB43097: xmalloc (xmalloc.c:147) ==11143== by 0x52A7F2: df_install_refs (df-scan.c:2454) ==11143== by 0x52AA8D: df_refs_add_to_chains (df-scan.c:2580) ==11143== by 0x52E0CF: df_record_exit_block_uses (df-scan.c:3950) ==11143== by 0x52F5E0: df_scan_blocks (df-scan.c:604) ==11143== by 0x51EF4D: rest_of_handle_df_initialize (df-core.c:743) ==11143== by 0x6686D6: execute_one_pass (passes.c:1284) ==11143== by 0x6688D0: execute_pass_list (passes.c:1334) ==11143== by 0x6688E4: execute_pass_list (passes.c:1335) ==11143== by 0x74A705: tree_rest_of_compilation (tree-optimize.c:421) ==11143== by 0x8FA841: cgraph_expand_function (cgraphunit.c:1148) ==11143== ==11143== LEAK SUMMARY: ==11143== definitely lost: 28,800 bytes in 413 blocks. ==11143== indirectly lost: 35,500 bytes in 347 blocks. ==11143== possibly lost: 64 bytes in 2 blocks. ==11143== still reachable: 298,303 bytes in 1,048 blocks. ==11143== suppressed: 0 bytes in 0 blocks. Notice the similarity in the second trace hunk to that found in pr36214. Also, the first trace hunk shown here, I have not seen before and involves simplify_parameter_variable. This may be the clue we need. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34828
next prev parent reply other threads:[~2008-05-26 17:05 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-17 16:15 [Bug fortran/34828] New: " burnus at gcc dot gnu dot org 2008-01-18 6:12 ` [Bug fortran/34828] " jvdelisle at gcc dot gnu dot org 2008-01-18 7:13 ` kargl at gcc dot gnu dot org 2008-01-18 23:33 ` jvdelisle at gcc dot gnu dot org 2008-01-20 3:41 ` kargl at gcc dot gnu dot org 2008-01-25 23:31 ` danglin at gcc dot gnu dot org 2008-01-28 9:10 ` jvdelisle at gcc dot gnu dot org 2008-01-28 9:17 ` jvdelisle at gcc dot gnu dot org 2008-01-28 9:21 ` jvdelisle at gcc dot gnu dot org 2008-01-28 9:53 ` dominiq at lps dot ens dot fr 2008-01-29 5:18 ` jvdelisle at gcc dot gnu dot org 2008-01-29 5:53 ` jvdelisle at gcc dot gnu dot org 2008-01-30 6:57 ` jvdelisle at gcc dot gnu dot org 2008-01-30 15:55 ` dominiq at lps dot ens dot fr 2008-01-30 18:29 ` Jerry_V_DeLisle at rl dot gov 2008-03-25 2:53 ` jvdelisle at gcc dot gnu dot org 2008-04-30 22:37 ` kargl at gcc dot gnu dot org 2008-05-26 17:05 ` jvdelisle at gcc dot gnu dot org [this message] 2008-05-28 17:27 ` fxcoudert at gcc dot gnu dot org 2008-08-08 20:54 ` jv244 at cam dot ac dot uk 2008-08-08 21:08 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-09 5:17 ` kargl at gcc dot gnu dot org 2008-08-11 7:36 ` jv244 at cam dot ac dot uk
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=20080526170507.29100.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).