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 gcc gm2 testsuite on x86_64-pc-linux-gnu
Date: Fri, 18 Nov 2022 13:05:14 +0000	[thread overview]
Message-ID: <E1ow13S-0020kO-DI@lancelot> (raw)

gcc-branch: devel/modula-2
git commit 1e33c0019babcb613313ee9a364b65274b4d45c7

Linux 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 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
GNU dejagnu: 1.6.2-1
GNU g++: 10.2.1-6
10.2.1-6
GNU libc: 2.31-13+deb11u3


Native configuration is x86_64-pc-linux-gnu

		=== gm2 tests ===


Running target unix
WARNING: gm2/isocoroutines/run/pass/coroutine.mod execution,  -O -g  program timed out.
FAIL: gm2/isocoroutines/run/pass/coroutine.mod execution,  -O -g 
FAIL: gm2/pim/pass/TestLong4.mod,  -O  
FAIL: gm2/pim/pass/TestLong4.mod,  -O -g  
FAIL: gm2/pim/pass/TestLong4.mod,  -O3 -fomit-frame-pointer  
FAIL: gm2/pim/pass/TestLong4.mod,  -O3 -fomit-frame-pointer -finline-functions  
FAIL: gm2/pim/pass/TestLong4.mod,  -Os  
FAIL: gm2/pim/pass/TestLong4.mod,  -g  

		=== gm2 Summary ===

# of expected passes		11831
# of unexpected failures	7

Compiler version: gcc gm2 
Platform: x86_64-pc-linux-gnu
configure flags: --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 --disable-bootstrap

             reply	other threads:[~2022-11-18 13:05 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 13:05 Gaius Mulley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-27 14:28 Gaius Mulley
2023-04-25 23:26 Gaius Mulley
2023-04-25 19:32 Gaius Mulley
2023-04-21 22:51 Gaius Mulley
2023-04-13 11:35 Gaius Mulley
2023-04-12 19:57 Gaius Mulley
2023-04-05 22:00 Gaius Mulley
2023-03-24 15:44 Gaius Mulley
2023-03-16 22:17 Gaius Mulley
2023-03-09 23:58 gaius
2023-03-09 17:20 gaius
2023-03-07 19:07 Gaius Mulley
2023-03-07 14:32 Gaius Mulley
2023-03-06 20:58 Gaius Mulley
2023-02-28 17:27 Gaius Mulley
2023-02-23 10:44 Gaius Mulley
2023-02-13 21:02 Gaius Mulley
2023-02-01 20:01 Gaius Mulley
2023-01-31  0:33 Gaius Mulley
2023-01-27 16:18 Gaius Mulley
2023-01-23 15:42 Gaius Mulley
2023-01-17 11:13 Gaius Mulley
2023-01-16 20:44 Gaius Mulley
2023-01-15 12:01 Gaius Mulley
2023-01-12 15:48 Gaius Mulley
2022-12-22 14:40 Gaius Mulley
2022-12-17  7:43 Gaius Mulley
2022-12-16 13:10 Gaius Mulley
2022-12-06 12:05 Gaius Mulley
2022-12-05 21:18 Gaius Mulley
2022-12-05 20:00 Gaius Mulley
2022-12-04 21:51 Gaius Mulley
2022-11-22 20:35 Gaius Mulley
2022-11-21 20:29 Gaius Mulley
2022-11-16 15:38 Gaius Mulley
2022-11-16  5:48 Gaius Mulley
2022-11-05  2:44 Gaius Mulley
2022-11-03 17:42 Gaius Mulley
2022-10-22  1:20 Gaius Mulley
2022-09-20 16:18 Gaius Mulley
2022-09-16 11:03 Gaius Mulley
2022-09-14 17:19 Gaius Mulley
2022-09-14 13:18 Gaius Mulley
2022-09-13 12:17 Gaius Mulley
2022-07-24 23:14 Gaius Mulley
2022-06-29 14:40 Gaius Mulley
2022-06-26 22:28 Gaius Mulley
2022-06-26 18:22 Gaius Mulley
2022-01-18 14:43 Gaius Mulley
2022-01-05 11:48 Gaius Mulley
2022-01-05 10:47 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=E1ow13S-0020kO-DI@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: link
Be 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).