public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/98584] Many D tests FAIL with SIGBUS in read_encoded_value_with_base Date: Tue, 20 Apr 2021 00:40:43 +0000 [thread overview] Message-ID: <bug-98584-4-AOlHeGpIR1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98584-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98584 --- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> --- Running all D torture tests on sparc-sun-solaris2.11 with the RUNTESTFLAGS --target_board=unix\{,-m64\}", I don't see any failures that arise in any f the supported tests now. --- === gdc Summary for unix === # of expected passes 1520 # of unsupported tests 300 === gdc Summary for unix/-m64 === # of expected passes 1520 # of unsupported tests 300 === gdc Summary === # of expected passes 3040 # of unsupported tests 600 --- A variant of this patch can be backported to the gcc-10 branch as well if it is useful.
prev parent reply other threads:[~2021-04-20 0:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-07 16:27 [Bug d/98584] New: " ro at gcc dot gnu.org 2021-04-20 0:28 ` [Bug d/98584] " cvs-commit at gcc dot gnu.org 2021-04-20 0:40 ` ibuclaw at gdcproject dot org [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-98584-4-AOlHeGpIR1@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).