public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36463] gfc_get_default_type(): Bad symbol
Date: Fri, 28 Nov 2008 12:53:00 -0000 [thread overview]
Message-ID: <20081128125222.4820.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36463-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from burnus at gcc dot gnu dot org 2008-11-28 12:52 -------
(In reply to comment #19)
> Since comment #13 is fixed, this should not be labeled a regression any more I
> guess. Are there still problems with comment #12 (apart from PR35810), or can
> we close this PR?
I think only PR 35971, comment 0 (with modification of PR 35971 comment 2) and
[essentially/exactly the same] comment 12 of this PR remain (= compiles, but
ICE at run time).
I don't see ad hoc whether PR 35810 is the problem; if you close this PR, can
you add a note to the PR that one should re-check PR 35971, comment 0 and PR
36463, comment 12 before closing? That way we are sure that the test case does
not get lost, if PR 35810 does not fix the remaining issues.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36463
next prev parent reply other threads:[~2008-11-28 12:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 9:55 [Bug fortran/36463] New: [4.4 Regression] ICE in expand_expr_real_1, at expr.c:7264 with rev.136554 dominiq at lps dot ens dot fr
2008-06-08 12:02 ` [Bug fortran/36463] " dominiq at lps dot ens dot fr
2008-06-09 9:08 ` dominiq at lps dot ens dot fr
2008-06-09 9:09 ` dominiq at lps dot ens dot fr
2008-06-11 11:15 ` jsm28 at gcc dot gnu dot org
2008-06-25 12:12 ` rguenth at gcc dot gnu dot org
2008-07-27 17:14 ` burnus at gcc dot gnu dot org
2008-07-27 17:20 ` burnus at gcc dot gnu dot org
2008-10-20 8:11 ` janus at gcc dot gnu dot org
2008-10-20 8:58 ` dominiq at lps dot ens dot fr
2008-10-20 9:20 ` janus at gcc dot gnu dot org
2008-10-20 12:03 ` janus at gcc dot gnu dot org
2008-11-01 13:26 ` janus at gcc dot gnu dot org
2008-11-01 13:53 ` [Bug fortran/36463] gfc_get_default_type(): Bad symbol janus at gcc dot gnu dot org
2008-11-01 14:07 ` janus at gcc dot gnu dot org
2008-11-01 14:22 ` [Bug fortran/36463] [4.4 regression] " janus at gcc dot gnu dot org
2008-11-11 15:37 ` mikael at gcc dot gnu dot org
2008-11-17 22:20 ` mikael at gcc dot gnu dot org
2008-11-17 22:57 ` janus at gcc dot gnu dot org
2008-11-18 13:24 ` mikael at gcc dot gnu dot org
2008-11-25 13:30 ` mikael at gcc dot gnu dot org
2008-11-28 11:55 ` [Bug fortran/36463] " janus at gcc dot gnu dot org
2008-11-28 12:53 ` burnus at gcc dot gnu dot org [this message]
2008-11-28 13:25 ` mikael at gcc dot gnu dot org
2008-11-28 13:49 ` janus at gcc dot gnu dot org
2008-11-29 11:27 ` janus 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=20081128125222.4820.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).