public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/86389] execute FAILs with -fipa-pta Date: Mon, 23 Aug 2021 11:21:27 +0000 [thread overview] Message-ID: <bug-86389-4-NVGgjOj4Jo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-86389-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86389 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> --- Using (C, C++ and Fortran) I see only the following execution failures: ./x86_64-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.log:FAIL: 25_algorithms/minmax_element/constrained.cc execution test ./x86_64-pc-linux-gnu/libstdc++-v3/testsuite/libstdc++.log:FAIL: 25_algorithms/mismatch/constrained.cc execution test ./gcc/testsuite/gfortran/gfortran.log:FAIL: gfortran.dg/vector_subscript_1.f90 -O1 execution test ./gcc/testsuite/gfortran/gfortran.log:FAIL: gfortran.dg/vector_subscript_1.f90 -O2 execution test ./gcc/testsuite/gfortran/gfortran.log:FAIL: gfortran.dg/vector_subscript_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test ./gcc/testsuite/gfortran/gfortran.log:FAIL: gfortran.dg/vector_subscript_1.f90 -O3 -g execution test ./gcc/testsuite/gfortran/gfortran.log:FAIL: gfortran.dg/vector_subscript_1.f90 -Os execution test
next parent reply other threads:[~2021-08-23 11:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-86389-4@http.gcc.gnu.org/bugzilla/> 2021-08-23 11:21 ` marxin at gcc dot gnu.org [this message] 2021-08-24 13:47 ` rguenth at gcc dot gnu.org 2021-08-24 14:15 ` rguenth at gcc dot gnu.org 2021-11-05 17:02 ` marxin at gcc dot gnu.org 2021-11-05 17:17 ` hubicka at gcc dot gnu.org 2021-11-08 8:13 ` rguenth 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-86389-4-NVGgjOj4Jo@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).