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 20231205 master r14-6185-g805be8fbeab351 (GCC) testsuite on x86_64-pc-linux-gnu Date: Wed, 06 Dec 2023 16:36:58 -0800 (PST) [thread overview] Message-ID: <E1rB2Nt-001aYT-2e@lancelot> (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 --enable-multilib --enable-plugin --enable-bootstrap gcc-branch: master git commit 805be8fbeab351dc3109aaa17fcc8cc6f74c8caa Linux 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 unknown GNU/Linux GNU ld (GNU Binutils for Debian) 2.40 GNU assembler (GNU Binutils for Debian) 2.40 GNU Make 4.3 Test run by gaius on Thu Dec 7 00:34:14 2023 Native configuration is x86_64-pc-linux-gnu === gm2 tests === Schedule of variations: unix FAIL: gm2/pim/fail/longtypes2.mod, -g FAIL: gm2/pim/fail/longtypes2.mod, -O FAIL: gm2/pim/fail/longtypes2.mod, -O -g FAIL: gm2/pim/fail/longtypes2.mod, -Os FAIL: gm2/pim/fail/longtypes2.mod, -O3 -fomit-frame-pointer FAIL: gm2/pim/fail/longtypes2.mod, -O3 -fomit-frame-pointer -finline-functions FAIL: gm2/pim/fail/longtypes3.mod, -g FAIL: gm2/pim/fail/longtypes3.mod, -O FAIL: gm2/pim/fail/longtypes3.mod, -O -g FAIL: gm2/pim/fail/longtypes3.mod, -Os FAIL: gm2/pim/fail/longtypes3.mod, -O3 -fomit-frame-pointer FAIL: gm2/pim/fail/longtypes3.mod, -O3 -fomit-frame-pointer -finline-functions === gm2 Summary === # of expected passes 12890 # of unexpected failures 12
next reply other threads:[~2023-12-07 0:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-07 0:36 Gaius Mulley [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-12-07 9:00 Gaius Mulley 2023-12-05 23:28 Gaius Mulley
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=E1rB2Nt-001aYT-2e@lancelot \ --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).