From: Tobias Burnus <burnus@net-b.de>
To: Mikael Morin <mikael.morin@sfr.fr>,
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, 27 Apr 2014 18:56:00 -0000 [thread overview]
Message-ID: <535D50B8.3070801@net-b.de> (raw)
In-Reply-To: <5322208C.1010002@sfr.fr>
Given that we are now in stage 1: Mikael and Bud, what's the status of
this patch?
http://gcc.gnu.org/ml/fortran/2014-03/msg00098.html
Tobias
On January 13, 2014 22:18, Mikael Morin wrote:
> Hello,
>
> Le 10/03/2014 03:15, jimmie.davis@l-3com.com a écrit :
>> Index: gcc/gcc/fortran/symbol.c
>> ===================================================================
>> --- gcc/gcc/fortran/symbol.c (revision 208437)
>> +++ gcc/gcc/fortran/symbol.c (working copy)
>> @@ -3069,56 +3069,56 @@
>>
>> FOR_EACH_VEC_ELT (latest_undo_chgset->syms, i, p)
>> {
>> - if (p->gfc_new)
>> + /* Symbol was new. Or was old and just put in common. */
> Now the comment needs updating as "just put in common" also applies to
> the "new" case. Or you can also remove it ("just put in common" is
> somewhat redundant with the other comment anyway).
>
>> + if ( p->attr.in_common && p->common_block && p->common_block->head
>> + && (p->gfc_new || !p->old_symbol->attr.in_common))
>> {
>> - /* Symbol was new. */
>> - if (p->attr.in_common && p->common_block && p->common_block->head)
>> - {
>> - /* If the symbol was added to any common block, it
>> - needs to be removed to stop the resolver looking
>> - for a (possibly) dead symbol. */
>> + /* If the symbol was added to any common block, it
>> + needs to be removed to stop the resolver looking
>> + for a (possibly) dead symbol. */
> "needs" should be aligned with "If" like it was before; same for "for".
>
> Now we are in pretty good shape.
>
> The ICE happens with invalid code after reporting an error, correct?
> Then I agree, this should rather wait for stage 1.
>
> Thanks
> Mikael
>
next prev parent reply other threads:[~2014-04-27 18:47 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
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 [this message]
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=535D50B8.3070801@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimmie.davis@l-3com.com \
--cc=mikael.morin@sfr.fr \
/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).