public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95503] [9/10/11 Regression] ICE in gfc_is_simply_contiguous, at fortran/expr.c:5844
Date: Thu, 11 Jun 2020 13:49:33 +0000	[thread overview]
Message-ID: <bug-95503-4-otLwwk1Meh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95503-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95503

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:87af4f40453a9c84363bde5d9a58466de7fbee2e

commit r11-1236-g87af4f40453a9c84363bde5d9a58466de7fbee2e
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Thu Jun 11 15:48:56 2020 +0200

    PR fortran/95503 - Fix ICE in gfc_is_simply_contiguous, at
fortran/expr.c:5844

    The check for assigning a pointer that cannot be determined to be simply
    contiguous at compile time to a contiguous pointer does not need to be
    invoked if the lhs of the assignment is known to have conflicting
attributes.

    2020-06-11  Harald Anlauf  <anlauf@gmx.de>

    gcc/fortran/
            PR fortran/95503
            * expr.c (gfc_check_pointer_assign): Skip contiguity check of rhs
            of pointer assignment if lhs cannot be simply contiguous.

    gcc/testsuite/
            PR fortran/95503
            * gfortran.dg/pr95503.f90: New test.

  parent reply	other threads:[~2020-06-11 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 15:46 [Bug fortran/95503] New: " gscfq@t-online.de
2020-06-03 18:40 ` [Bug fortran/95503] " anlauf at gcc dot gnu.org
2020-06-03 22:04 ` [Bug fortran/95503] [9/10/11 Regression] " tkoenig at gcc dot gnu.org
2020-06-04 18:48 ` anlauf at gcc dot gnu.org
2020-06-11 13:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-14 12:40 ` cvs-commit at gcc dot gnu.org
2020-06-14 13:04 ` cvs-commit at gcc dot gnu.org
2020-06-14 13:28 ` anlauf at gcc dot gnu.org

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=bug-95503-4-otLwwk1Meh@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).