public inbox for gcc-testresults@sourceware.org help / color / mirror / Atom feed
From: Gaius Mulley <gaiusmod2@gmail.com> To: gcc-testresults@gcc.gnu.org Subject: Results for 20230725 master r14-2759-g50656980497d77 (GCC) testsuite on i686-pc-linux-gnu Date: Tue, 25 Jul 2023 19:18:37 -0700 (PDT) [thread overview] Message-ID: <E1qOU6l-0002NF-3B@astolat> (raw) $ ../configure --prefix=/home/gaius/opt --libexecdir=/home/gaius/opt/lib --enable-host-shared --enable-threads=posix --enable-clocale=gnu --enable-checking --enable-long-longx --enable-languages=m2 --with-build-config=bootstrap-lto-lean --disable-multilib --enable-bootstrap gcc-branch: master git commit 50656980497d77ac12a5e7179013a6af09ba32f7 Linux 5.10.0-14-686-pae #1 SMP Debian 5.10.113-1 (2022-04-29) i686 unknown GNU/Linux GNU ld (GNU Binutils for Debian) 2.35.2 GNU assembler (GNU Binutils for Debian) 2.35.2 GNU Make 4.3 Test run by gaius on Wed Jul 26 03:14:17 2023 Native configuration is i686-pc-linux-gnu === gm2 tests === Schedule of variations: unix FAIL: gm2/isolib/run/pass/seqappend.mod execution, -g FAIL: gm2/isolib/run/pass/seqappend.mod execution, -O FAIL: gm2/isolib/run/pass/seqappend.mod execution, -O -g FAIL: gm2/isolib/run/pass/seqappend.mod execution, -Os FAIL: gm2/isolib/run/pass/seqappend.mod execution, -O3 -fomit-frame-pointer FAIL: gm2/isolib/run/pass/seqappend.mod execution, -O3 -fomit-frame-pointer -finline-functions FAIL: gm2/pim/pass/TestLong4.mod, -g FAIL: gm2/pim/pass/TestLong4.mod, -O FAIL: gm2/pim/pass/TestLong4.mod, -O -g FAIL: gm2/pim/pass/TestLong4.mod, -Os FAIL: gm2/pim/pass/TestLong4.mod, -O3 -fomit-frame-pointer FAIL: gm2/pim/pass/TestLong4.mod, -O3 -fomit-frame-pointer -finline-functions === gm2 Summary === # of expected passes 12469 # of unexpected failures 12
reply other threads:[~2023-07-26 2:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1qOU6l-0002NF-3B@astolat \ --to=gaiusmod2@gmail.com \ --cc=gcc-testresults@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).