public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	       gcc-patches <gcc-patches@gcc.gnu.org>,
	Harald Anlauf <anlauf@gmx.de>
Subject: Re: [patch, fortran] Implement IS_CONTINUOUS intrinsic
Date: Sun, 06 Jan 2019 22:40:00 -0000	[thread overview]
Message-ID: <20190106224030.GA64155@troutmask.apl.washington.edu> (raw)
In-Reply-To: <a56e0a95-5b42-ee3c-508c-e00b3e9375b5@netcologne.de>

On Sun, Jan 06, 2019 at 11:04:12PM +0100, Thomas Koenig wrote:
> 
> the attached patch builds on a long history:  Tobias Burnus created
> an original version in 2012. Harald Anlauf recently picked it up,
> (see https://gcc.gnu.org/ml/fortran/2019-01/msg00012.html).
> polished it and made it ready for gcc-9.  This already worked
> quite well.  I added a bit of compile-time simplification (where we can
> prove an array is not contiguous). The original library function version
> was by Harald, but I replaced that with something simpler; also the
> code would have pushed the limits for contributions without
> (yet) a copyright assignment in place.
> 
> Later, we can also use the gfc_is_not_contiguous to reject
> obvious errors when assigning to contiguous pointers or
> arguments.
> 
> Regression-tested on x86_64-pc-linux-gnu. OK for trunk?
> 

OK.

Thanks Thomas, Harald, and Tobias!

-- 
Steve

      reply	other threads:[~2019-01-06 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 22:04 Thomas Koenig
2019-01-06 22:40 ` Steve Kargl [this message]

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=20190106224030.GA64155@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).