public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "furue at hawaii dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99506] New: internal compiler error: in record_reference, at cgraphbuild.c:64
Date: Wed, 10 Mar 2021 06:32:37 +0000 [thread overview]
Message-ID: <bug-99506-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99506
Bug ID: 99506
Summary: internal compiler error: in record_reference, at
cgraphbuild.c:64
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: furue at hawaii dot edu
Target Milestone: ---
Created attachment 50346
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50346&action=edit
tar including all the source files.
The internal compiler error happens with GNU Fortran (Homebrew GCC 10.2.0_4)
10.2.0 . The homebrew maintainer confirms this error and further reports that
the same error occurs on Ubuntu, too (I don't know the version of gfortran).
See https://github.com/Homebrew/homebrew-core/issues/72865 . The maintainer
recommends submitting this report here.
Expand the attached tar file, cd to that directory, and on the command line:
````
$ gfortran -c numeric_kinds.f90
$ gfortran -c indices.f90
$ gfortran fix-track-partials-00.f90 indices.o
f951: internal compiler error: in record_reference, at cgraphbuild.c:64
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://github.com/Homebrew/homebrew-core/issues> for instructions.
````
In the above the dollar symbols is the command prompt.
next reply other threads:[~2021-03-10 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 6:32 furue at hawaii dot edu [this message]
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
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@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).