From: Mikael Morin <mikael.morin@sfr.fr>
To: jimmie.davis@l-3com.com, gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: patch fortran, pr 59746, internal compiler error : segmentation fault
Date: Sun, 09 Mar 2014 17:31:00 -0000 [thread overview]
Message-ID: <531CA574.2050900@sfr.fr> (raw)
In-Reply-To: <FFF95760268D324AB6DD9426E83C8DF70B2E0F21@ARLEXCHMBX01.lst.link.l-3com.com>
Hello,
Le 09/03/2014 13:59, jimmie.davis@l-3com.com a écrit :
>
>
> The code would only remove a variable from a common block if it was just defined in the previous statement. The PR showed a case where a pre-existing variable was put in the common block. When it was not removed, the common block list was wrong and segfaulted (or infinite looped) when used later on.
>
> I changed it so it would remove a variable from a common block if it was just defined, or if it previously existed and was put in the common block in the last statement.
>
> This patch works with the example given in the PR and has no regressions in the testsuite.
>
> tested i686/linux.
>
>
> --bud davis
>
[...]
> Index: gcc/gcc/fortran/symbol.c
> ===================================================================
> --- gcc/gcc/fortran/symbol.c (revision 208437)
> +++ gcc/gcc/fortran/symbol.c (working copy)
> @@ -3069,9 +3069,9 @@
>
> FOR_EACH_VEC_ELT (latest_undo_chgset->syms, i, p)
> {
> - if (p->gfc_new)
> + if (p->gfc_new || (p->attr.in_common && !p->old_symbol->attr.in_common) )
> {
> - /* Symbol was new. */
> + /* Symbol was new. Or was old and just put in common */
> if (p->attr.in_common && p->common_block && p->common_block->head)
Please merge the two ifs; it seems they have exactly the same scope
after the patch.
> {
> /* If the symbol was added to any common block, it
> @@ -3115,6 +3115,9 @@
> /* The derived type is saved in the symtree with the first
> letter capitalized; the all lower-case version to the
> derived type contains its associated generic function. */
This comment applies to the TOUPPER thing below...
> + }
> + if (p->gfc_new)
> + {
... so it should be put here. Also the indentation is wrong.
> if (p->attr.flavor == FL_DERIVED)
> gfc_delete_symtree (&p->ns->sym_root, gfc_get_string ("%c%s",
> (char) TOUPPER ((unsigned char) p->name[0]),
> @@ -3125,7 +3128,9 @@
> gfc_release_symbol (p);
> }
> else
> - restore_old_symbol (p);
> + {
> + restore_old_symbol (p);
> + }
> }
This is unnecessary.
Otherwise looks goodish. This is not a regression, but I suppose it
will be acceptable.
Mikael
next prev parent reply other threads:[~2014-03-09 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 13:57 jimmie.davis
2014-03-09 17:31 ` Mikael Morin [this message]
2014-03-09 20:35 ` jimmie.davis
2014-03-09 21:38 ` Mikael Morin
2014-03-10 7:49 ` jimmie.davis
2014-03-13 21:24 ` Mikael Morin
2014-04-27 18:56 ` Tobias Burnus
2015-07-29 19:18 ` Mikael Morin
2015-08-06 10:11 ` *ping* " Mikael Morin
2015-08-06 10:28 ` Paul Richard Thomas
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=531CA574.2050900@sfr.fr \
--to=mikael.morin@sfr.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimmie.davis@l-3com.com \
/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).