public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105182] [11/12 Regression] compiling NJOY21 causes a ICE segmentation fault: 11
Date: Thu, 07 Apr 2022 21:23:45 +0000	[thread overview]
Message-ID: <bug-105182-4-p8CtLebklP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105182-4@http.gcc.gnu.org/bugzilla/>

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

kargl at gcc dot gnu.org changed:

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

--- Comment #11 from kargl at gcc dot gnu.org ---
Remove myself from CC list.  I do not have 11.x source tree.  Minimum example
that should have been supplied by someone else.

module errorm

   implicit none

   integer :: ngn, nis, isrr, nscr4
   real, dimension(:), allocatable::egn

   contains

      subroutine resprx(nwscr,a)
         integer :: nwscr
         real :: a(nwscr)
         integer :: iest, ieed
         integer, parameter :: mxlru2=10
         real::amur(3,mxlru2)
         do isrr=1, nis
            call rpxunr(a,amur,mxlru2,iest,ieed,nwscr)
         enddo
      end subroutine resprx

      subroutine rpxunr(a,amur,mxlru2,iest,ieed,nwscr)
         integer::mxlru2,iest,ieed,nwscr
         real::a(nwscr),amur(3,mxlru2)
         integer::ii
         integer,parameter::maxe=60
         real::sig(maxe,5)
         real::gsigr(4,25)
         ngn = 10
         allocate(egn(ngn))
         call rpxgrp(ngn,egn,sig,ii,gsigr,a,nwscr)
      end subroutine rpxunr

      subroutine covout
         integer:: nwds
         real,dimension(:),allocatable::scr
         nwds = 10
         allocate(scr(nwds))
         call resprx(nwds,scr)
      end subroutine covout

      subroutine rpxgrp(igx, egn, sig, ipoint, gsig, a, nwscr)
         integer :: igx, ipoint, nwscr
         integer, parameter:: maxe=60
         real :: egn(*), sig(maxe,5), gsig(4,25), a(nwscr)
      end subroutine rpxgrp

end module errorm

  parent reply	other threads:[~2022-04-07 21:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 15:59 [Bug fortran/105182] New: " kermitnuc at gmail dot com
2022-04-06 17:06 ` [Bug fortran/105182] " kargl at gcc dot gnu.org
2022-04-06 20:50 ` kermitnuc at gmail dot com
2022-04-06 20:57 ` sgk at troutmask dot apl.washington.edu
2022-04-06 21:54 ` kermitnuc at gmail dot com
2022-04-06 23:38 ` sgk at troutmask dot apl.washington.edu
2022-04-07  1:09 ` kermitnuc at gmail dot com
2022-04-07  2:58 ` sgk at troutmask dot apl.washington.edu
2022-04-07  4:51 ` kargl at gcc dot gnu.org
2022-04-07  7:08 ` [Bug fortran/105182] [11/12 Regression] " rguenth at gcc dot gnu.org
2022-04-07  7:08 ` rguenth at gcc dot gnu.org
2022-04-07 19:47 ` kargl at gcc dot gnu.org
2022-04-07 21:23 ` kargl at gcc dot gnu.org [this message]
2022-04-07 21:35 ` anlauf at gcc dot gnu.org
2022-04-07 21:41 ` kargl at gcc dot gnu.org
2022-04-07 21:58 ` anlauf at gcc dot gnu.org
2022-04-07 22:35 ` sgk at troutmask dot apl.washington.edu
2022-04-08  8:04 ` gscfq@t-online.de
2022-04-08 16:04 ` kargl at gcc dot gnu.org
2022-04-10 15:43 ` kermitnuc at gmail dot com

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-105182-4-p8CtLebklP@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).