public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/94246] [9/10 Regression] valgrind error for ./gfortran.dg/bessel_5.f90 since r9-1566-g87c789f1c0b2df41 Date: Mon, 23 Mar 2020 19:29:02 +0000 [thread overview] Message-ID: <bug-94246-4-Pj8cjJSWMb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94246-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94246 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #7 from anlauf at gcc dot gnu.org --- I get an ICE even for the non-valgrind version on x86_64-pc-linux-gnu: gcc/testsuite/gfortran.dg/bessel_5.f90:64:50: 64 | if (any (BESSEL_YN(0, 10, 0.0) /= [ (BESSEL_YN(i, 0.0), i = 0, 10) ])) & | 1 Error: Result of BESSEL_YN overflows its kind at (1) gcc/testsuite/gfortran.dg/bessel_5.f90:64:26: 64 | if (any (BESSEL_YN(0, 10, 0.0) /= [ (BESSEL_YN(i, 0.0), i = 0, 10) ])) & | 1 Error: Result of BESSEL_YN is -INF at (1) f951: internal compiler error: Segmentation fault 0xd4aedf crash_signal ../../gcc-trunk/gcc/toplev.c:328 0x65ae4f reduce_binary_ac ../../gcc-trunk/gcc/fortran/arith.c:1325 0x65aee2 reduce_binary_ac ../../gcc-trunk/gcc/fortran/arith.c:1312 0x65b034 reduce_binary ../../gcc-trunk/gcc/fortran/arith.c:1438 0x65b35b eval_intrinsic ../../gcc-trunk/gcc/fortran/arith.c:1613 0x6965f8 simplify_intrinsic_op ../../gcc-trunk/gcc/fortran/expr.c:1219 0x6965f8 gfc_simplify_expr(gfc_expr*, int) ../../gcc-trunk/gcc/fortran/expr.c:2233 0x708c89 resolve_operator ../../gcc-trunk/gcc/fortran/resolve.c:4377 0x706177 gfc_resolve_expr(gfc_expr*) ../../gcc-trunk/gcc/fortran/resolve.c:7022 0x70993f gfc_resolve_expr(gfc_expr*) ../../gcc-trunk/gcc/fortran/resolve.c:2162 0x70993f resolve_actual_arglist ../../gcc-trunk/gcc/fortran/resolve.c:2081 0x70654e resolve_function ../../gcc-trunk/gcc/fortran/resolve.c:3183 0x70654e gfc_resolve_expr(gfc_expr*) ../../gcc-trunk/gcc/fortran/resolve.c:7029 0x70e7d1 gfc_resolve_expr(gfc_expr*) ../../gcc-trunk/gcc/fortran/resolve.c:6996 0x70e7d1 gfc_resolve_blocks(gfc_code*, gfc_namespace*) ../../gcc-trunk/gcc/fortran/resolve.c:10618 0x6fe518 gfc_resolve_code(gfc_code*, gfc_namespace*) ../../gcc-trunk/gcc/fortran/resolve.c:11706 0x700d9d resolve_codes ../../gcc-trunk/gcc/fortran/resolve.c:17233 0x700e6e gfc_resolve(gfc_namespace*) ../../gcc-trunk/gcc/fortran/resolve.c:17268 0x6ef01d resolve_all_program_units ../../gcc-trunk/gcc/fortran/parse.c:6245 0x6ef01d gfc_parse_file() ../../gcc-trunk/gcc/fortran/parse.c:6492 I agree with Richard that this should not happen.
next prev parent reply other threads:[~2020-03-23 19:29 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-21 9:14 [Bug fortran/94246] New: valgrind error for ./gfortran.dg/bessel_5.f90 dcb314 at hotmail dot com 2020-03-21 10:34 ` [Bug fortran/94246] [9/10 Regression] valgrind error for ./gfortran.dg/bessel_5.f90 since r9-1566-g87c789f1c0b2df41 marxin at gcc dot gnu.org 2020-03-21 21:10 ` kargl at gcc dot gnu.org 2020-03-21 22:27 ` dcb314 at hotmail dot com 2020-03-21 23:04 ` sgk at troutmask dot apl.washington.edu 2020-03-23 7:35 ` rguenth at gcc dot gnu.org 2020-03-23 16:21 ` sgk at troutmask dot apl.washington.edu 2020-03-23 19:29 ` anlauf at gcc dot gnu.org [this message] 2020-03-23 19:54 ` anlauf at gcc dot gnu.org 2020-03-23 20:20 ` sgk at troutmask dot apl.washington.edu 2020-03-24 17:48 ` pault at gcc dot gnu.org 2020-04-01 9:58 ` burnus at gcc dot gnu.org 2020-04-29 20:52 ` [Bug fortran/94246] [9 " anlauf at gcc dot gnu.org 2020-07-13 19:58 ` dominiq at lps dot ens.fr 2021-01-04 8:15 ` cvs-commit at gcc dot gnu.org 2021-01-04 9:08 ` pault 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-94246-4-Pj8cjJSWMb@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).