From: Fritz Reese <fritzoreese@gmail.com>
To: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING -- [PATCH, fortran] PR 85982 -- ICE in resolve_component
Date: Wed, 1 Apr 2020 14:00:01 -0400 [thread overview]
Message-ID: <CAE4aFAmwtfQsDkfjPzoSZjhBa1qS9_O8C7_X6j3Ean6QBVv42Q@mail.gmail.com> (raw)
In-Reply-To: <CAE4aFAm5gGyyLjkp=Ne8ea5V4X2=g=OmtGcUPb03unMB2DT1NQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Wed, Apr 1, 2020 at 1:19 PM Fritz Reese <fritzoreese@gmail.com> wrote:
[...]
> is still good. Is this OK to commit to trunk and for backport? I'd
> like to port as far back as 7.
I realized 7 branch is closed. I would backport to 8.
> gcc/testsuite/ChangeLog:
> 2020-04-01 Fritz Reese <foreese@gcc.gnu.org>
>
> PR fortran/85982
> * gfortran.dg/dec_structure_28.f90: New test.
Forgot to include the testcase in the patch. Testcase is attached.
[-- Attachment #2: dec_structure_28.f90 --]
[-- Type: text/x-fortran, Size: 1379 bytes --]
! { dg-do compile }
! { dg-options "-fdec-structure -fdec-static" }
!
! PR fortran/85982
!
! Test a regression wherein some component attributes were erroneously accepted
! within a DEC structure.
!
structure /s/
integer :: a
integer, intent(in) :: b ! { dg-error "is not allowed" }
integer, intent(out) :: c ! { dg-error "is not allowed" }
integer, intent(inout) :: d ! { dg-error "is not allowed" }
integer, dimension(1,1) :: e ! OK
integer, external, pointer :: f ! { dg-error "is not allowed" }
integer, intrinsic :: f ! { dg-error "is not allowed" }
integer, optional :: g ! { dg-error "is not allowed" }
integer, parameter :: h ! { dg-error "is not allowed" }
integer, protected :: i ! { dg-error "is not allowed" }
integer, private :: j ! { dg-error "is not allowed" }
integer, static :: k ! { dg-error "is not allowed" }
integer, automatic :: l ! { dg-error "is not allowed" }
integer, public :: m ! { dg-error "is not allowed" }
integer, save :: n ! { dg-error "is not allowed" }
integer, target :: o ! { dg-error "is not allowed" }
integer, value :: p ! { dg-error "is not allowed" }
integer, volatile :: q ! { dg-error "is not allowed" }
integer, bind(c) :: r ! { dg-error "is not allowed" }
integer, asynchronous :: t ! { dg-error "is not allowed" }
character(len=3) :: v ! OK
integer(kind=4) :: w ! OK
end structure
end
next prev parent reply other threads:[~2020-04-01 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 17:19 Fritz Reese
2020-04-01 18:00 ` Fritz Reese [this message]
2020-04-02 7:50 ` Tobias Burnus
2020-04-02 16:20 ` Fritz Reese
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=CAE4aFAmwtfQsDkfjPzoSZjhBa1qS9_O8C7_X6j3Ean6QBVv42Q@mail.gmail.com \
--to=fritzoreese@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).