public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103628] ICE: Segmentation fault (in gfc_conv_tree_to_mpfr) Date: Thu, 17 Feb 2022 06:39:11 +0000 [thread overview] Message-ID: <bug-103628-4-uyb9uSllCd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103628-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103628 --- Comment #2 from Arseny Solokha <asolokha at gmx dot com> --- Indeed. Sorry. So could you cd flang/test/f90_correct/src and than invoke gfortran the following way instead: % powerpc-e300c3-linux-gnu-gfortran-12.0.1 -w -c check_mod.f90 qp54.f08 f951: internal compiler error: Segmentation fault 0xf264e6 crash_signal /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-12.0.1_p20220213/work/gcc-12-20220213/gcc/toplev.cc:322 <…> ?
next prev parent reply other threads:[~2022-02-17 6:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 11:16 [Bug target/103628] New: " asolokha at gmx dot com 2022-02-16 22:38 ` [Bug target/103628] " seurer at gcc dot gnu.org 2022-02-17 6:39 ` asolokha at gmx dot com [this message] 2022-02-17 13:46 ` seurer at gcc dot gnu.org 2022-02-18 4:26 ` asolokha at gmx dot com 2023-02-22 9:00 ` guihaoc at gcc dot gnu.org 2023-03-24 2:48 ` cvs-commit at gcc dot gnu.org 2023-03-24 14:53 ` segher at gcc dot gnu.org
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-103628-4-uyb9uSllCd@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).