public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin 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 07:53:26 +0000 [thread overview] Message-ID: <bug-99506-4-lFVveVvPiQ@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 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Priority|P3 |P4 Last reconfirmed| |2021-03-10 Version|unknown |11.0 Ever confirmed|0 |1 CC| |marxin at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Reduced test-case: module numeric_kinds integer, parameter :: single = kind(1.0) integer, parameter :: double = selected_real_kind(2*precision(1.0_single)) end module numeric_kinds module indices contains function find_idx(x, xx) result(idx) end function find_idx function nearest_idx(x, xx) result(idx) if (x < xx0) then if (xx0 - x < 0/2) then end if end if do if (dl >= 0 .and. last_dl <= 0) then end if end do end function nearest_idx function close_enough_idx(x, xx, eps, verbose) result(res) logical, intent(in), optional:: verbose if (abs0 <= eps) then if (present(verbose)) then if (verbose .eqv. .true.) then end if end if end if end function close_enough_idx end module indices program fix_track_partials use numeric_kinds, only: double character(*), parameter:: & youf = "track-partial-nws200-y-grid.dat" integer, parameter:: & lonw100 = 10000, lats100 = -4000, dlon100 = 10, dlat100 = 10 integer, parameter:: imax = 50, jmax = 350 integer, dimension(*), parameter:: & latt100 = [((lats100 + dlat100 * j - dlat100/2), j=1,jmax)] real(double), dimension(*), parameter:: & latt = [(latt100(i)/100.d0, j=1,jmax)] real(double), dimension(:), allocatable:: xs, ys, xs_fixed, ys_fixed call move_to_nearest(ys_fixed, pnts=ys, axis=latt) contains subroutine read_track(xs, ys, file) end subroutine read_track subroutine save_track(xs, ys, file) end subroutine save_track subroutine move_to_nearest(res, pnts, axis) real(double), intent(out):: res(:) real(double), intent(in) :: pnts(:), axis(:) end subroutine move_to_nearest subroutine extend_arr_double(arr, idx, mes) end subroutine extend_arr_double subroutine shrink_arr_double(arr, idx, mes) end subroutine shrink_arr_double end program fix_track_partials It's very old, at least as old as GCC 4.8.0.
next prev parent reply other threads:[~2021-03-10 7:53 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 ` marxin at gcc dot gnu.org [this message] 2021-03-10 8:00 ` [Bug fortran/99506] " kargl at gcc dot gnu.org 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-lFVveVvPiQ@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).