public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44584] gfortran.dg/typebound_proc_15.f03 failed
Date: Fri, 18 Jun 2010 21:24:00 -0000 [thread overview]
Message-ID: <20100618212412.2683.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44584-682@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from janus at gcc dot gnu dot org 2010-06-18 21:24 -------
(In reply to comment #0)
> On Linux/ia64, revision 160858 gave
> ...
> Revision 160826 is OK.
The only Fortran-related change in this range is
r160834 | janus | 2010-06-16 14:54:54 +0200 (Wed, 16 Jun 2010) | 17 lines
This was the fix for PR44549, which was a follow-up to PR40117 (where
typebound_proc_15.f03 came from).
Can you confirm that this is the culprit?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44584
next prev parent reply other threads:[~2010-06-18 21:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 18:31 [Bug middle-end/44584] New: [4.6 Regression] gfortran.dg/typebound_proc_15.f03 hjl dot tools at gmail dot com
2010-06-18 21:18 ` [Bug fortran/44584] gfortran.dg/typebound_proc_15.f03 failed janus at gcc dot gnu dot org
2010-06-18 21:24 ` janus at gcc dot gnu dot org [this message]
2010-06-18 22:11 ` hjl dot tools at gmail dot com
2010-06-18 22:15 ` hjl dot tools at gmail dot com
2010-06-18 23:54 ` janus at gcc dot gnu dot org
2010-06-19 0:48 ` hjl dot tools at gmail dot com
2010-06-19 21:20 ` [Bug fortran/44584] [4.6 Regression] " janus at gcc dot gnu dot org
2010-06-20 0:06 ` janus at gcc dot gnu dot org
2010-06-20 0:12 ` janus at gcc dot gnu dot org
2010-06-21 14:32 ` hjl dot tools at gmail dot com
2010-06-21 20:58 ` hjl dot tools at gmail dot com
2010-06-21 21:01 ` hjl dot tools at gmail dot com
2010-06-24 21:35 ` [Bug fortran/44584] [4.6 Regression] Invalid memory access with gfortran.dg/typebound_proc_15.f03 rguenth at gcc dot gnu dot org
2010-07-30 9:38 ` janus at gcc dot gnu dot org
2010-07-30 10:23 ` mikael at gcc dot gnu dot org
2010-07-30 11:00 ` mikael at gcc dot gnu dot org
2010-07-30 12:05 ` mikael at gcc dot gnu dot org
2010-08-03 11:09 ` janus at gcc dot gnu dot org
2010-08-03 11:14 ` janus at gcc dot gnu dot org
2010-08-04 0:28 ` hjl dot tools at gmail dot com
2010-08-04 7:10 ` ubizjak at gmail dot com
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=20100618212412.2683.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).