From: Mark Eggleston <mark.eggleston@codethink.co.uk>
To: Jeff Law <law@redhat.com>, sgk@troutmask.apl.washington.edu
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH] Automatics in equivalence statements
Date: Fri, 16 Aug 2019 15:51:00 -0000 [thread overview]
Message-ID: <1bf8a6ac-7b4b-81f9-53a5-d57a33d1d53d@codethink.co.uk> (raw)
In-Reply-To: <e0e9fe43-9a26-5983-d9e6-9889fc6acfee@redhat.com>
On 14/08/2019 18:10, Jeff Law wrote:
> On 8/14/19 2:45 AM, Mark Eggleston wrote:
>> I now have commit access.
>>
>> gcc/fortran
>>
>> Â Â Â Jeff Law <law@redhat.com>
>> Â Â Â Mark Eggleston <mark.eggleston@codethink.com>
>>
>> Â Â Â * gfortran.h: Add gfc_check_conflict declaration.
>> Â Â Â * symbol.c (check_conflict): Rename cfg_check_conflict and remove
>> Â Â Â static.
>> Â Â Â * symbol.c (cfg_check_conflict): Remove automatic in equivalence
>> Â Â Â conflict check.
>> Â Â Â * symbol.c (save_symbol): Add check for in equivalence to stop the
>> Â Â Â the save attribute being added.
>> Â Â Â * trans-common.c (build_equiv_decl): Add is_auto parameter and
>> Â Â Â add !is_auto to condition where TREE_STATIC (decl) is set.
>> Â Â Â * trans-common.c (build_equiv_decl): Add local variable is_auto,
>> Â Â Â set it true if an atomatic attribute is encountered in the variable
>>    list. Call build_equiv_decl with is_auto as an additional parameter.
>> Â Â Â flag_dec_format_defaults is enabled.
>> Â Â Â * trans-common.c (accumulate_equivalence_attributes) : New subroutine.
>> Â Â Â * trans-common.c (find_equivalence) : New local variable dummy_symbol,
>> Â Â Â accumulated equivalence attributes from each symbol then check for
>> Â Â Â conflicts.
>>
>> gcc/testsuite
>>
>> Â Â Â Mark Eggleston <mark.eggleston@codethink.com>
>>
>> Â Â Â * gfortran.dg/auto_in_equiv_1.f90: New test.
>> Â Â Â * gfortran.dg/auto_in_equiv_2.f90: New test.
>> Â Â Â * gfortran.dg/auto_in_equiv_3.f90: New test.
>>
>> OK to commit?
>>
>> How do I know that I have approval to commit?
> Yes, this is OK to commit. Steve acked it in a private message to me.
Committed as revision 274565.
> Normally you'll get an ACK/OK on the public list. But private ACKs or
> ACKs on IRC also count as approval :-)
>
> jeff
>
--
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2019-08-16 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe0dee5c-e2d7-5e69-94e4-0a807f9f0886@redhat.com>
[not found] ` <20190723013806.GA12299@troutmask.apl.washington.edu>
[not found] ` <3497ca30-0bd6-ac0a-0069-098f25de44d3@redhat.com>
[not found] ` <20190723023614.GA12520@troutmask.apl.washington.edu>
[not found] ` <cd31af75-cc5a-3cab-1993-21f431a6f09f@redhat.com>
2019-08-14 8:49 ` Mark Eggleston
2019-08-14 17:24 ` Jeff Law
2019-08-16 15:51 ` Mark Eggleston [this message]
2019-09-28 20:33 ` Andreas Schwab
2019-09-30 10:25 ` Jakub Jelinek
2019-10-02 13:39 ` Mark Eggleston
2019-06-21 13:31 Mark Eggleston
2019-06-21 14:10 ` Steve Kargl
2019-06-24 8:19 ` Bernhard Reutner-Fischer
2019-06-24 13:47 ` Mark Eggleston
2019-06-24 23:18 ` Jeff Law
2019-06-25 13:17 ` Mark Eggleston
2019-07-01 9:35 ` Mark Eggleston
2019-07-23 0:23 ` Jeff Law
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=1bf8a6ac-7b4b-81f9-53a5-d57a33d1d53d@codethink.co.uk \
--to=mark.eggleston@codethink.co.uk \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rep.dot.nop@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
/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).