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/107595] ICE in ix86_push_argument, at config/i386/i386.cc:4335
Date: Thu, 17 Nov 2022 21:29:39 +0000	[thread overview]
Message-ID: <bug-107595-4-2K8YQH4mTC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107595-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anlauf at gcc dot gnu.org

--- Comment #6 from anlauf at gcc dot gnu.org ---
Slight reduction of the testcase:

program p
  type t
     integer, pointer :: b
  end type
! type(t) :: x = t(null())   ! OK
  type(t)    x  /t(null())/  ! ICE
  if (associated (x%b)) stop
end

Comparing the -fdump-fortran-original for both variants:

@@ -15,7 +15,7 @@
     result: associated
   symtree: 'null'        || symbol: 'null'         
     type spec : (INTEGER 4)
-    attributes: (PROCEDURE INTRINSIC-PROC  FUNCTION IMPLICIT-TYPE
ARRAY-OUTER-DEPENDENCY)
+    attributes: (PROCEDURE  FUNCTION IMPLICIT-TYPE ARRAY-OUTER-DEPENDENCY)
     result: null
   symtree: 'p'           || symbol: 'p'            
     type spec : (UNKNOWN 0)
@@ -27,8 +27,8 @@
     result: t
   symtree: 'x'           || symbol: 'x'            
     type spec : (DERIVED t)
-    attributes: (VARIABLE IMPLICIT-SAVE)
-    value: t(NULL())
+    attributes: (VARIABLE  DATA)
+    value: t(null[()])

   code:
   IF _gfortran_associated[[((p:x % b) ((arg not-present)))]]


Are we just missing the resolution of NULL() in the failing case early enough?

      parent reply	other threads:[~2022-11-17 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 17:55 [Bug fortran/107595] New: " gscfq@t-online.de
2022-11-09 21:17 ` [Bug fortran/107595] [13 Regression] " hjl.tools at gmail dot com
2022-11-09 22:28 ` kargl at gcc dot gnu.org
2022-11-09 22:29 ` kargl at gcc dot gnu.org
2022-11-10  7:25 ` rguenth at gcc dot gnu.org
2022-11-10 19:11 ` anlauf at gcc dot gnu.org
2022-11-10 19:12 ` [Bug fortran/107595] " pinskia at gcc dot gnu.org
2022-11-17 21:29 ` anlauf at gcc dot gnu.org [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=bug-107595-4-2K8YQH4mTC@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).