public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	       "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] (Partial) Implementation of simplificaiton of CSHIFT
Date: Sat, 21 Nov 2015 19:26:00 -0000	[thread overview]
Message-ID: <20151121192622.GA81197@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAMe9rOrv0tj2r6c1W482gcqj+BGdkYrPVS04AQGiVnrpdb8RcA@mail.gmail.com>

On Sat, Nov 21, 2015 at 11:19:22AM -0800, H.J. Lu wrote:
> On Sat, Nov 21, 2015 at 10:20 AM, Steve Kargl
> <sgk@troutmask.apl.washington.edu> wrote:
> > On Sat, Nov 21, 2015 at 10:07:35AM -0800, H.J. Lu wrote:
> >> On Sat, Nov 21, 2015 at 8:26 AM, Steve Kargl
> >> <sgk@troutmask.apl.washington.edu> wrote:
> >> > On Sat, Nov 21, 2015 at 11:41:51AM +0100, Paul Richard Thomas wrote:
> >> >>
> >> >> Just a couple of small typos:
> >> >> "Unexpected expr_type cause an ICE" ;  causes?
> >> >> "! An array of derived types workd too." ; works?
> >> >>
> >> >> Apart from that it's OK for trunk.
> >> >>
> >> >> Thanks for the patch
> >> >>
> >> >
> >> > Thanks for the the review.  I don't have a clue as
> >> > to how to do simplification for rank > 2. :(
> >> >
> >>
> >> It breaks bootstrap:
> >>
> >>   int dm;
> >>
> >>   /* DIM is only useful for rank > 1, but deal with it here as one can
> >>      set DIM = 1 for rank = 1.  */
> >>   if (dim)
> >>     {
> >>       if (!gfc_is_constant_expr (dim))
> >> return NULL;
> >>       dm = mpz_get_si (dim->value.integer);
> >>     }
> >>   else
> >>     dm = 1;
> >>
> >> dm is set, but never used.
> >>
> >
> > Perhaps, bootstrap needs to set appropriate warning levels.
> 
> https://gcc.gnu.org/ml/gcc-regression/2015-11/msg00648.html
> 

See 5 lines up.

-- 
Steve

  reply	other threads:[~2015-11-21 19:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20  0:58 Steve Kargl
2015-11-20  1:31 ` Steve Kargl
2015-11-20  3:16   ` Steve Kargl
2015-11-20 20:09 ` Steve Kargl
2015-11-21 10:41   ` Paul Richard Thomas
2015-11-21 16:27     ` Steve Kargl
2015-11-21 18:07       ` H.J. Lu
2015-11-21 18:20         ` Steve Kargl
2015-11-21 19:19           ` H.J. Lu
2015-11-21 19:26             ` Steve Kargl [this message]
2015-11-21 20:07               ` Steve Kargl
2015-11-21 22:26                 ` Eric Botcazou
2015-11-21 22:39                   ` Steve Kargl
2015-12-31 14:00                 ` Gerald Pfeifer
2015-12-31 16:13                   ` Steve Kargl
2015-11-21 18:23         ` Tim Prince
2015-11-21 20:22 Dominique d'Humières
2015-11-21 20:30 ` Steve Kargl
2015-11-22  8:51   ` Dominique d'Humières
2015-11-22 16:21     ` Steve Kargl
2015-11-22 18:06       ` Dominique d'Humières

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=20151121192622.GA81197@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=paul.richard.thomas@gmail.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).