public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: Dominique Dhumieres <dominiq@lps.ens.fr>,
	gcc-patches@gcc.gnu.org,        fortran@gcc.gnu.org
Subject: Re: [PATCH] fortran/65429 -- don't dereference a null pointer
Date: Wed, 22 Apr 2015 23:18:00 -0000	[thread overview]
Message-ID: <20150422231818.GA47679@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20150407195920.GA17421@troutmask.apl.washington.edu>

On Tue, Apr 07, 2015 at 12:59:20PM -0700, Steve Kargl wrote:
> On Tue, Mar 31, 2015 at 10:17:14AM -0700, Jerry DeLisle wrote:
> > On 03/29/2015 09:25 AM, Steve Kargl wrote:
> > > On Sat, Mar 28, 2015 at 01:01:57AM +0100, Dominique Dhumieres wrote:
> > >>
> > >> AFAICT your test succeeds without your patch and does not test that the ICE
> > >> reported by FX is gone (indeed it is with your patch).
> > >>
> > >
> > > New patch and testcase.  The ChangeLog entries are in the
> > > original email.  Built and tested on x86_64-*-freebsd.
> > > OK, now?
> > >
> > 
> > OK Steve.
> 
> I just checked and this is not a regression with respect
> to 4.6, 4.7. 4.8, or 4.9.  As 5.0 is coming soon, I'll
> for stage 1 to commit.
> 

Fixed with the following

r222342 trunk
r222343 5.1 branch

-- 
Steve

  reply	other threads:[~2015-04-22 23:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28  0:02 Dominique Dhumieres
2015-03-28  0:33 ` Steve Kargl
2015-03-28 11:42   ` Dominique d'Humières
2015-03-28 14:50     ` Steve Kargl
2015-03-28 15:17       ` Dominique d'Humières
2015-03-29 16:25 ` Steve Kargl
2015-03-31 17:17   ` Jerry DeLisle
2015-04-07 19:59     ` Steve Kargl
2015-04-22 23:18       ` Steve Kargl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-27 22:47 Steve Kargl
2015-03-27 23:50 ` Tobias Burnus

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=20150422231818.GA47679@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=dominiq@lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle@charter.net \
    /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).