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/99506] internal compiler error: in record_reference, at cgraphbuild.c:64
Date: Wed, 10 Mar 2021 08:00:11 +0000	[thread overview]
Message-ID: <bug-99506-4-mjTkDyfFJ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99506-4@http.gcc.gnu.org/bugzilla/>

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

kargl at gcc dot gnu.org changed:

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

--- Comment #2 from kargl at gcc dot gnu.org ---
First, the compiler should not ICE.
Second, your program likely has a bug, which is the cause of the ICE.
Third, it's not clear if the middle-end can detect the issue.
Fourth, it's clear the Fortran front-end does not catch the problem.
Finally, here's a better reduced testcase.

program fix_track_partials

  implicit none

  integer, parameter :: double = 8
  integer, parameter :: lats100 = -4000,  dlat100 = 10
  integer, parameter :: jmax = 350
  integer  i, j

  integer, parameter:: &
      latt100(jmax) = [((lats100 + dlat100 * j - dlat100/2), j=1,jmax)]

   real(double),  parameter:: latt(jmax) = [(latt100(i)/100.d0, j=1,jmax)]

   real(double), allocatable:: ys(:), ys_fixed(:)

   ys = [1]
   call move_to_nearest(ys_fixed, pnts=ys, axis=latt)

   contains

      subroutine move_to_nearest(res, pnts, axis)
         real(double), intent(out):: res(:)
         real(double), intent(in) :: pnts(:), axis(:)
      end subroutine move_to_nearest

end program fix_track_partials

  parent reply	other threads:[~2021-03-10  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  6:32 [Bug fortran/99506] New: " furue at hawaii dot edu
2021-03-10  7:53 ` [Bug fortran/99506] " marxin at gcc dot gnu.org
2021-03-10  8:00 ` kargl at gcc dot gnu.org [this message]
2021-03-10  8:18 ` furue at hawaii dot edu
2021-03-10  8:39 ` rguenth at gcc dot gnu.org
2021-03-10 16:52 ` sgk at troutmask dot apl.washington.edu
2021-03-10 22:22 ` anlauf at gcc dot gnu.org
2021-03-10 22:59 ` sgk at troutmask dot apl.washington.edu
2021-03-11  1:38 ` sgk at troutmask dot apl.washington.edu

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-99506-4-mjTkDyfFJ3@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).