public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60898] [4.8/4.9/5 Regression] model compile error with gfortran 4.7 and gcc 4.9
Date: Sat, 14 Feb 2015 15:27:00 -0000 [thread overview]
Message-ID: <bug-60898-4-9BDXxgvFlH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60898-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60898
--- Comment #18 from Mikael Morin <mikael at gcc dot gnu.org> ---
Created attachment 34756
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34756&action=edit
patch fixing comment #7
(In reply to Mikael Morin from comment #17)
> Using Tobias' analysis in comment #14, there is an "obvious" fix, augmenting
> the reference count of the symbols present in the vector (untested):
>
This is not enough.
There is some code in resolve_symbol that reassigns some this_symtree->n.sym,
and may call gfc_release_symbol. The problem being there is no check that
this_symtree->n.sym == sym, so that we may apply gfc_free_symbol to something
that remains reachable through this_symtree->n.sym.
next prev parent reply other threads:[~2015-02-14 15:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 3:06 [Bug fortran/60898] New: model compile error with gfortran 4.7 and gcc 4.9 on Mac OS 10.9 shaojuncycle at gmail dot com
2014-04-21 13:02 ` [Bug fortran/60898] " dominiq at lps dot ens.fr
2014-04-23 1:49 ` shaojuncycle at gmail dot com
2014-04-23 2:49 ` jvdelisle at gcc dot gnu.org
2014-05-02 10:30 ` dominiq at lps dot ens.fr
2014-07-13 12:51 ` dominiq at lps dot ens.fr
2014-07-13 12:55 ` dominiq at lps dot ens.fr
2014-07-13 21:51 ` jvdelisle at gcc dot gnu.org
2014-07-15 16:17 ` dominiq at lps dot ens.fr
2014-07-15 16:31 ` [Bug fortran/60898] [4.8/4.9/4.10 Regression] model compile error with gfortran 4.7 and gcc 4.9 dominiq at lps dot ens.fr
2014-07-15 16:34 ` dominiq at lps dot ens.fr
2014-07-15 18:03 ` anlauf at gmx dot de
2014-11-19 13:28 ` [Bug fortran/60898] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2014-12-01 11:57 ` rguenth at gcc dot gnu.org
2014-12-01 22:30 ` burnus at gcc dot gnu.org
2014-12-19 13:35 ` jakub at gcc dot gnu.org
2015-02-10 14:34 ` jvdelisle at gcc dot gnu.org
2015-02-10 15:25 ` mikael at gcc dot gnu.org
2015-02-14 15:27 ` mikael at gcc dot gnu.org [this message]
2015-02-14 15:42 ` dominiq at lps dot ens.fr
2015-02-14 19:00 ` mikael at gcc dot gnu.org
2015-02-15 10:45 ` dominiq at lps dot ens.fr
2015-02-16 14:13 ` mikael at gcc dot gnu.org
2015-03-08 11:53 ` mikael at gcc dot gnu.org
2015-03-12 16:09 ` mikael at gcc dot gnu.org
2015-03-12 17:59 ` 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-60898-4-9BDXxgvFlH@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).