public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janus Weil <janus@gcc.gnu.org>
To: Richard Biener <rguenther@suse.de>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
	gfortran <fortran@gcc.gnu.org>,
		gcc-patches <gcc-patches@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>
Subject: Re: [Patch, Fortran, F08] PR 84313: reject procedure pointers in COMMON blocks
Date: Tue, 13 Feb 2018 21:16:00 -0000	[thread overview]
Message-ID: <CAKwh3qhc4DJn1pQah7OEHu8J_3RQ0LeW0tTVnmypVy90UchxRw@mail.gmail.com> (raw)
In-Reply-To: <A6E7A4DE-0AC9-4680-B3F0-82CA3723D963@suse.de>

2018-02-13 20:55 GMT+01:00 Richard Biener <rguenther@suse.de>:
> On February 13, 2018 8:14:33 PM GMT+01:00, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
>>On Tue, Feb 13, 2018 at 07:24:35PM +0100, Janus Weil wrote:
>>>
>>> As my last submission, this fixes fallout from
>>>
>>https://groups.google.com/forum/?fromgroups#!topic/comp.lang.fortran/AIHRQ2kJv3c.
>>> As the last one, it is a very simple fix for an accepts-invalid
>>> problem (which is not a regression), so I hope this one will also
>>> still be suitable for trunk (if not, I hope the release managers, in
>>> CC, will stop me).
>>>
>>> It does regtest cleanly on x86_64-linux-gnu. Ok for trunk?
>>>
>>
>>Ok.

Thanks, Steve. Committed as r257636.


>>I think you can skip waiting RM approval.  To me, this patch
>>falls into the "too simply and obvious" fix category.
>>
>>PS: Given the response I got yesterday on the #gcc IRC channel
>>when I asked about the current status of trunk, I'm inclined to
>>ignore the "regression and doc fixes only" status.
>
> Heh! Fortran is not release critical so if it's broken we'll release anyway. Which means it's up to frontend maintainers to decide what they accept at this stage.

This is how it was handled for earlier releases also.

Nevertheless there is also quite a number of Fortran regression we
should take care of. Will try to have a look on the weekend.

Cheers,
Janus

  reply	other threads:[~2018-02-13 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 18:24 Janus Weil
2018-02-13 19:14 ` Steve Kargl
2018-02-13 19:55   ` Richard Biener
2018-02-13 21:16     ` Janus Weil [this message]
2018-02-14 11:30 ` Jakub Jelinek
2018-02-14 11:48   ` Jakub Jelinek
2018-02-14 12:09     ` Janus Weil
2018-02-14 15:57       ` Janus Weil

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=CAKwh3qhc4DJn1pQah7OEHu8J_3RQ0LeW0tTVnmypVy90UchxRw@mail.gmail.com \
    --to=janus@gcc.gnu.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    --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).