public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Thomas Koenig <tkoenig@netcologne.de>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Error for non-contiguous pointers
Date: Sat, 07 Oct 2017 01:46:00 -0000	[thread overview]
Message-ID: <4242ba5e-8263-19bb-a96a-2be0b8e750fd@charter.net> (raw)
In-Reply-To: <559678ec-7c1e-11f8-0fa6-0ec339d48359@netcologne.de>

On 10/03/2017 11:35 AM, Thomas Koenig wrote:
> Hello world,
> 
> I have re-thought and simplified the patch for PR49232.
> This now uses gfc_is_simply_contiguous, in the
> non-strict version.  I have also opted for an error
> because, well, the use cases rejected by this are really
> errors, and will very likely lead to wrong code in
> user applications.
> 
> Regression-tested. OK for trunk?

OK

Thanks for patch

> 
>     Thomas
> 
> 2017-10-03  Thomas Koenig  <tkoenig@gcc.gnu.org>
> 
>         PR fortran/49232
>         * expr.c (gfc_check_pointer_assign): Error
>         for non-contiguous rhs.
> 
> 2017-10-03  Thomas Koenig  <tkoenig@gcc.gnu.org>
> 
>         PR fortran/49232
>         * gfortran.dg/contiguous_4.f90: New test.
> 

      reply	other threads:[~2017-10-07  1:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 18:35 Thomas Koenig
2017-10-07  1:46 ` Jerry DeLisle [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=4242ba5e-8263-19bb-a96a-2be0b8e750fd@charter.net \
    --to=jvdelisle@charter.net \
    --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).