public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/106856] [12/13 Regression][OOP] CLASS attribute handling / ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 since r12-4346-geb92cd57a1ebe7cd Date: Tue, 06 Dec 2022 22:23:32 +0000 [thread overview] Message-ID: <bug-106856-4-gs6kZPooW3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106856-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #3 from anlauf at gcc dot gnu.org --- Created attachment 54030 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54030&action=edit Incremental patch The above patch on top of Tobias' initial one fixes some minor issues with it and improves the behavior for testcase class_75.f90 modified as follows: ! { dg-do compile } ! { dg-additional-options "-fcoarray=single" } ! ! PR fortran/106856 ! ! ! subroutine foo(x,y) class(*), optional :: x, y optional :: x ! { dg-error "Duplicate OPTIONAL attribute" } target :: x allocatable :: x target :: x ! { dg-error "Duplicate TARGET attribute" } allocatable :: x ! { dg-error "Duplicate ALLOCATABLE attribute" } pointer :: y contiguous :: y pointer :: y ! { dg-error "Duplicate POINTER attribute" } contiguous :: y ! { dg-error "Duplicate CONTIGUOUS attribute" } dimension :: x(:,:) dimension :: y(:,:,:) codimension :: x[:] ! < duplicat error for dimension/codimension: TODO add decl. ! Currently gives an ICE :-( end Note that these patches "regress" as follows: - gfortran.dg/interface_41.f90 - this had a bogus error on valid code! (Removing the dg-error fixes it.) - gfortran.dg/pr69398.f90 - this ICEs due to the duplicate DIMENSION attribute I tried to modify restore_old_symbol() to handle CLASS arrays, but then we ICE along a different path. Not sure if this is the right approach. Nevertheless, the patch as is already appears to be a great step forward!
next prev parent reply other threads:[~2022-12-06 22:23 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 17:12 [Bug fortran/106856] New: [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 gscfq@t-online.de 2022-09-07 8:26 ` [Bug fortran/106856] " rguenth at gcc dot gnu.org 2022-09-07 12:02 ` [Bug fortran/106856] [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 since r12-4346-geb92cd57a1ebe7cd marxin at gcc dot gnu.org 2022-09-08 8:52 ` burnus at gcc dot gnu.org 2022-12-06 22:23 ` anlauf at gcc dot gnu.org [this message] 2023-03-01 21:36 ` [Bug fortran/106856] [12/13 Regression][OOP] CLASS attribute handling / " anlauf at gcc dot gnu.org 2023-03-02 20:51 ` anlauf at gcc dot gnu.org 2023-03-02 22:04 ` anlauf at gcc dot gnu.org 2023-03-04 15:19 ` anlauf at gcc dot gnu.org 2023-03-05 20:13 ` cvs-commit at gcc dot gnu.org 2023-03-06 17:08 ` anlauf at gcc dot gnu.org 2023-03-06 17:11 ` anlauf at gcc dot gnu.org 2023-03-06 17:13 ` anlauf at gcc dot gnu.org 2023-03-06 17:15 ` anlauf at gcc dot gnu.org 2023-03-06 17:18 ` anlauf at gcc dot gnu.org 2023-03-06 17:50 ` anlauf at gcc dot gnu.org 2023-03-26 18:38 ` [Bug fortran/106856] [12 " anlauf at gcc dot gnu.org 2023-03-27 18:43 ` cvs-commit at gcc dot gnu.org 2023-03-27 18:47 ` anlauf at gcc dot gnu.org 2023-04-08 18:48 ` anlauf at gcc dot gnu.org 2023-11-25 19:06 ` 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-106856-4-gs6kZPooW3@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: linkBe 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).