public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drikosev at otenet dot gr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59016] f951: internal compiler error: Segmentation fault Date: Sun, 05 Apr 2015 09:19:00 -0000 [thread overview] Message-ID: <bug-59016-4-XxqyqNsf4l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59016-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59016 --- Comment #15 from drikosev at otenet dot gr --- Created attachment 35230 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35230&action=edit altered patch for the regressions reported in comment 11 Hi, As it seems the problem with the program bug.f90 is that the generic attribute is set in a symbol as the parser tries to match a declaration type specification; but finally, the statement isn't matched as such and the generic attribute wasn't cleared. So, the attached patch makes the cleanup, without causing the regressions listed in comment 9. The question here is if gfortran had to print an error message for this program: module types public :: undefined end module types write (*,*) "undefined types!" end --------------------------------------------------------------------------- PS: I've not checked out the source code from a repo, so the attached patch is just the output of the diff command (not svn diff).
next prev parent reply other threads:[~2015-04-05 9:19 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-06 8:48 [Bug fortran/59016] New: " Joost.VandeVondele at mat dot ethz.ch 2013-11-17 19:09 ` [Bug fortran/59016] " janus at gcc dot gnu.org 2013-12-21 19:35 ` bdavis at gcc dot gnu.org 2013-12-21 19:49 ` dominiq at lps dot ens.fr 2013-12-21 19:50 ` dominiq at lps dot ens.fr 2014-12-06 10:07 ` Joost.VandeVondele at mat dot ethz.ch 2015-03-29 20:38 ` drikosev at otenet dot gr 2015-03-29 22:02 ` drikosev at otenet dot gr 2015-04-03 13:49 ` dominiq at lps dot ens.fr 2015-04-03 17:01 ` drikosev at otenet dot gr 2015-04-04 9:02 ` dominiq at lps dot ens.fr 2015-04-04 9:31 ` dominiq at lps dot ens.fr 2015-04-04 9:41 ` drikosev at otenet dot gr 2015-04-04 10:47 ` drikosev at otenet dot gr 2015-04-05 9:19 ` drikosev at otenet dot gr [this message] 2015-04-05 11:50 ` dominiq at lps dot ens.fr 2015-04-05 13:03 ` dominiq at lps dot ens.fr 2015-04-05 14:37 ` dominiq at lps dot ens.fr 2015-04-05 16:37 ` drikosev at otenet dot gr 2015-04-05 16:42 ` dominiq at lps dot ens.fr 2015-04-05 19:13 ` drikosev at otenet dot gr 2015-04-05 23:23 ` drikosev at otenet dot gr 2015-04-06 19:14 ` dominiq at lps dot ens.fr 2015-04-06 21:26 ` dominiq at lps dot ens.fr 2015-04-07 18:57 ` jvdelisle at gcc dot gnu.org 2015-04-08 7:54 ` drikosev at otenet dot gr 2015-04-10 11:30 ` mikael at gcc dot gnu.org 2015-04-14 9:18 ` mikael at gcc dot gnu.org 2015-04-14 12:24 ` mikael at gcc dot gnu.org 2015-04-14 12:42 ` mikael at gcc dot gnu.org 2015-04-14 12:43 ` mikael at gcc dot gnu.org 2015-04-14 12:44 ` mikael at gcc dot gnu.org 2015-04-14 12:49 ` mikael 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-59016-4-XxqyqNsf4l@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: linkBe 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).