public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57129] [4.7/4.8/4.9 Regression] ICE (segfault) in check_extended_derived_type
Date: Sat, 18 Jan 2014 23:51:00 -0000 [thread overview]
Message-ID: <bug-57129-4-8DYKjHqAPJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57129-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57129
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> On darwin12/13 I don't get the ICE even for r201916.
I don't know what I did. After rechecking I found that r202804 gives the ICE
and r202825 does not.
The error is now
pr57129.f90:2.8:
type t
1
Error: FUNCTION attribute conflicts with SUBROUTINE attribute in 't' at (1)
pr57129.f90:3.5:
end type t
1
Error: Expecting END SUBROUTINE statement at (1)
pr57129.f90:4.18:
type, extends(t) :: t2
1
Error: Symbol 't' at (1) has not been previously defined
pr57129.f90:5.5:
end type t2
1
Error: Expecting END SUBROUTINE statement at (1)
The errors such as
Error: Symbol 't' at (1) has not been previously defined
comes from r202823.
So r202823 is likely to have fixed this PR.
next prev parent reply other threads:[~2014-01-18 23:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 21:53 [Bug fortran/57129] New: " burnus at gcc dot gnu.org
2013-05-15 13:28 ` [Bug fortran/57129] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-12-31 14:14 ` janus at gcc dot gnu.org
2014-01-06 22:27 ` dominiq at lps dot ens.fr
2014-01-18 20:29 ` mikael at gcc dot gnu.org
2014-01-18 21:18 ` dominiq at lps dot ens.fr
2014-01-18 23:36 ` dominiq at lps dot ens.fr
2014-01-18 23:51 ` dominiq at lps dot ens.fr [this message]
2014-01-19 11:10 ` janus at gcc dot gnu.org
2014-01-19 13:52 ` [Bug fortran/57129] [4.7/4.8/4.9 Regression] Improve error message for conflicts between PROCEDURE and DERIVED dominiq at lps dot ens.fr
2014-02-09 21:48 ` janus at gcc dot gnu.org
2014-06-12 13:46 ` [Bug fortran/57129] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:39 ` [Bug fortran/57129] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:22 ` [Bug fortran/57129] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:12 ` [Bug fortran/57129] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:36 ` jakub at gcc dot gnu.org
2020-04-18 20:36 ` [Bug fortran/57129] [8/9/10 " anlauf at gcc dot gnu.org
2020-04-19 11:07 ` cvs-commit 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=bug-57129-4-8DYKjHqAPJ@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).