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: Fri, 18 Feb 2022 04:26:09 +0000	[thread overview]
Message-ID: <bug-103628-4-NjNpdIxD3L@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 #4 from Arseny Solokha <asolokha at gmx dot com> ---
Yes, I actually have both. But that's the peculiarity of the way I build my
test corpus, which I build from multiple sources, and not really important.
Sorry for mistakenly pointing you at the wrong file copied from the source
other what was originally mentioned in the PR.

After reducing qp54.f08 and check_mod.F90 together, the testcase boils down to
the following:

program main
  integer, parameter :: k = 16
  real(kind = k):: b = 4h1234
end program main

  parent reply	other threads:[~2022-02-18  4:26 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
2022-02-17 13:46 ` seurer at gcc dot gnu.org
2022-02-18  4:26 ` asolokha at gmx dot com [this message]
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-NjNpdIxD3L@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).