public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ismail at pardus dot org dot tr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34907]  New: valgrind error indication from testsuite trans-types.c: gfc_typenode_for_spec
Date: Mon, 21 Jan 2008 22:03:00 -0000	[thread overview]
Message-ID: <bug-34907-10490@http.gcc.gnu.org/bugzilla/> (raw)

Valgrind shows,

FAIL: gfortran.dg/char_cshift_1.f90  -O0  (test for excess errors)
Excess errors:
==28334== Conditional jump or move depends on uninitialised value(s)
==28334==    at 0x811A4B9: gfc_typenode_for_spec (trans-types.c:848)
==28334==    by 0x810041F: gfc_conv_intrinsic_conversion
(trans-intrinsic.c:265)
==28334==    by 0x8108A81: gfc_conv_intrinsic_function (trans-intrinsic.c:3822)
==28334==    by 0x80FCE9D: gfc_conv_function_expr (trans-expr.c:3033)
==28334==    by 0x80FE23B: gfc_conv_expr (trans-expr.c:3537)
==28334==    by 0x80FE5E3: gfc_conv_expr_reference (trans-expr.c:3660)
==28334==    by 0x80FB74B: gfc_conv_function_call (trans-expr.c:2428)
==28334==    by 0x810370F: gfc_conv_intrinsic_funcall (trans-intrinsic.c:1641)
==28334==    by 0x8108811: gfc_conv_intrinsic_function (trans-intrinsic.c:3727)
==28334==    by 0x80FCE9D: gfc_conv_function_expr (trans-expr.c:3033)
==28334==    by 0x80FE23B: gfc_conv_expr (trans-expr.c:3537)
==28334==    by 0x80E42C9: gfc_add_loop_ss_code (trans-array.c:1902)


-- 
           Summary: valgrind error indication from testsuite trans-types.c:
                    gfc_typenode_for_spec
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ismail at pardus dot org dot tr
  GCC host triplet: i686-linux-gnu


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


             reply	other threads:[~2008-01-21 21:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 22:03 ismail at pardus dot org dot tr [this message]
2008-01-21 22:06 ` [Bug middle-end/34907] " ismail at pardus dot org dot tr
2008-01-21 22:07 ` ismail at pardus dot org dot tr
2008-01-21 23:20 ` [Bug fortran/34907] " burnus at gcc dot gnu dot org
2008-01-21 23:34 ` burnus at gcc dot gnu dot org
2008-01-22  4:12 ` jvdelisle at gcc dot gnu dot org
2008-01-22 17:10 ` burnus at gcc dot gnu dot org
2008-02-16 16:47 ` jvdelisle at gcc dot gnu dot org
2008-02-16 18:23 ` jvdelisle at gcc dot gnu dot org
2008-02-22  6:23 ` jvdelisle at gcc dot gnu dot org
2008-02-27  4:39 ` jvdelisle at gcc dot gnu 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-34907-10490@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: 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).