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/34907] valgrind error indication from testsuite trans-types.c: gfc_typenode_for_spec
Date: Sat, 16 Feb 2008 18:23:00 -0000 [thread overview]
Message-ID: <20080216182238.5768.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34907-10490@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from jvdelisle at gcc dot gnu dot org 2008-02-16 18:22 -------
Here is the culprit:
Index: iresolve.c
===================================================================
--- iresolve.c (revision 132355)
+++ iresolve.c (working copy)
@@ -585,6 +585,7 @@ gfc_resolve_cshift (gfc_expr *f, gfc_exp
if (shift->ts.kind < m)
{
gfc_typespec ts;
+ gfc_clear_ts (&ts);
ts.type = BT_INTEGER;
ts.kind = m;
gfc_convert_type_warn (shift, &ts, 2, 0);
This fixes it. There are a bunch of these in iresolve.c I will fix them all
for 4.4
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34907
next prev parent reply other threads:[~2008-02-16 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 22:03 [Bug middle-end/34907] New: " ismail at pardus dot org dot tr
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 [this message]
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=20080216182238.5768.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).