public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vital.had at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/95706] New test case gfortran.dg/pr95690.f90 fails Date: Sat, 29 Apr 2023 16:35:13 +0000 [thread overview] Message-ID: <bug-95706-4-dMMK4SlYXv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95706-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95706 Sergey Fedorov <vital.had at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vital.had at gmail dot com --- Comment #15 from Sergey Fedorov <vital.had at gmail dot com> --- Also happens on powerpc-apple-darwin with gcc13: Executing on host: /Users/svacchanda/GCC_test/gcc_devel/gcc/testsuite/gfortran1/../../gfortran -B/Users/svacchanda/GCC_test/gcc_devel/gcc/testsuite/gfortran1/../../ -B/Users/svacchanda/GCC_test/gcc_devel/powerpc-apple-darwin10/./libgfortran/ /Users/svacchanda/GCC_sources/gcc-git/gcc/testsuite/gfortran.dg/pr95690.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -S -o pr95690.s (timeout = 300) spawn -ignore SIGHUP /Users/svacchanda/GCC_test/gcc_devel/gcc/testsuite/gfortran1/../../gfortran -B/Users/svacchanda/GCC_test/gcc_devel/gcc/testsuite/gfortran1/../../ -B/Users/svacchanda/GCC_test/gcc_devel/powerpc-apple-darwin10/./libgfortran/ /Users/svacchanda/GCC_sources/gcc-git/gcc/testsuite/gfortran.dg/pr95690.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -S -o pr95690.s /Users/svacchanda/GCC_sources/gcc-git/gcc/testsuite/gfortran.dg/pr95690.f90:5:21: Error: initializer for floating value is not a floating constant compiler exited with status 1 FAIL: gfortran.dg/pr95690.f90 -O (test for errors, line 6) FAIL: gfortran.dg/pr95690.f90 -O (test for excess errors)
prev parent reply other threads:[~2023-04-29 16:35 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-16 18:06 [Bug testsuite/95706] New: " seurer at linux dot vnet.ibm.com 2020-06-17 6:32 ` [Bug testsuite/95706] " rguenth at gcc dot gnu.org 2020-06-17 14:54 ` seurer at linux dot vnet.ibm.com 2020-06-17 14:56 ` rguenther at suse dot de 2020-06-18 14:24 ` clyon at gcc dot gnu.org 2020-06-25 11:06 ` rguenth at gcc dot gnu.org 2020-06-25 11:06 ` rguenth at gcc dot gnu.org 2020-07-02 6:42 ` rguenth at gcc dot gnu.org 2020-07-02 7:02 ` rguenth at gcc dot gnu.org 2020-07-02 9:21 ` rguenth at gcc dot gnu.org 2020-07-02 21:08 ` ro at gcc dot gnu.org 2020-07-02 21:17 ` dje at gcc dot gnu.org 2020-07-03 10:12 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-12-14 16:33 ` danglin at gcc dot gnu.org 2023-04-02 15:41 ` danglin at gcc dot gnu.org 2023-04-29 16:35 ` vital.had at gmail dot com [this message]
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-95706-4-dMMK4SlYXv@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).