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/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95
Date: Sun, 06 Dec 2009 01:03:00 -0000	[thread overview]
Message-ID: <20091206010242.29481.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36534-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from jvdelisle at gcc dot gnu dot org  2009-12-06 01:02 -------
OK we have a Heisenbug going on here.

Running from Valgrind like this:

 valgrind --leak-check=full f951 -pedantic <untitled.f
==14463== Memcheck, a memory error detector.
==14463== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==14463== Using LibVEX rev 1804, a library for dynamic binary translation.
==14463== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==14463== Using valgrind-3.3.0, a dynamic binary instrumentation framework.
==14463== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==14463== For more details, rerun with: -v
==14463== 
Warning: Reading file '<stdin>' as free form
        .file   "<stdin>"
:2.51:

      PARAMETER ( MY_STRING4 = (/ "A" , "B", "C" /) )
                                                   1
Warning: Obsolescent feature: CHARACTER(*) function '__convert_s1_s4' at (1)

---- snip ----

==14463== 316 bytes in 2 blocks are definitely lost in loss record 2 of 6
==14463==    at 0x4A05174: calloc (vg_replace_malloc.c:397)
==14463==    by 0xCD3CA8: xcalloc (xmalloc.c:162)
==14463==    by 0x629AF4: init_emit (emit-rtl.c:5565)
==14463==    by 0x6C2CB7: prepare_function_start (function.c:4169)
==14463==    by 0x6C2D58: init_function_start (function.c:4217)
==14463==    by 0x53B5FD: trans_function_start (trans-decl.c:1925)
==14463==    by 0x5423FE: gfc_generate_function_code (trans-decl.c:4272)
==14463==    by 0x4EF4F3: gfc_parse_file (parse.c:4223)
==14463==    by 0x52587C: gfc_be_parse_file (f95-lang.c:239)
==14463==    by 0x81B205: toplev_main (toplev.c:1049)
==14463==    by 0x3F6841E329: (below main) (libc-start.c:220)
==14463== 
==14463== LEAK SUMMARY:
==14463==    definitely lost: 316 bytes in 2 blocks.
==14463==      possibly lost: 64 bytes in 2 blocks.
==14463==    still reachable: 423,076 bytes in 1,336 blocks.
==14463==         suppressed: 0 bytes in 0 blocks.
==14463== Reachable blocks (those to which a pointer was found) are not shown.
==14463== To see them, rerun with: --leak-check=full --show-reachable=yes


-- 


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


  parent reply	other threads:[~2009-12-06  1:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 21:34 [Bug fortran/36534] New: " burnus at gcc dot gnu dot org
2008-06-13 23:06 ` [Bug fortran/36534] " fxcoudert at gcc dot gnu dot org
2008-06-14  5:15 ` jvdelisle at gcc dot gnu dot org
2008-07-09 22:56 ` fxcoudert at gcc dot gnu dot org
2008-07-18 13:29 ` burnus at gcc dot gnu dot org
2008-08-23  8:15 ` fxcoudert at gcc dot gnu dot org
2008-08-24 10:39 ` burnus at gcc dot gnu dot org
2009-12-05  6:56 ` jvdelisle at gcc dot gnu dot org
2009-12-05 18:28 ` tkoenig at gcc dot gnu dot org
2009-12-05 18:54 ` burnus at gcc dot gnu dot org
2009-12-06  0:16 ` jvdelisle at gcc dot gnu dot org
2009-12-06  1:03 ` jvdelisle at gcc dot gnu dot org [this message]
2010-04-13  4:31 ` jvdelisle at gcc dot gnu dot org
2010-05-02 14:31 ` dfranke at gcc dot gnu dot org
     [not found] <bug-36534-4@http.gcc.gnu.org/bugzilla/>
2014-09-27 15:22 ` fxcoudert at gcc dot gnu.org
2014-09-29  8:33 ` fxcoudert at gcc dot gnu.org
2014-10-04 10:19 ` 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=20091206010242.29481.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: 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).