public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/96393] New: [11 regression] All 32-bit execution tests FAIL: internal error printing module cycle
Date: Thu, 30 Jul 2020 22:10:59 +0000	[thread overview]
Message-ID: <bug-96393-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96393

            Bug ID: 96393
           Summary: [11 regression] All 32-bit execution tests FAIL:
                    internal error printing module cycle
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: ro at gcc dot gnu.org
  Target Milestone: ---
            Target: i386-pc-solaris2.11, sparc-sun-solaris2.11

Between 20200729 (f6fe3bbf9f6c0b7249933e19b94560b6b26bf269) and 20200730
(561a19c3011f7bde3a41f2a27ea979118e3a2dff), all 32-bit D execution tests began
to FAIL on (at least) Solaris/SPARC and Solaris/x86, all with the same error:

object.Error@(0): internal error printing module cycle

The 64-bit tests seem to be unchanged.

             reply	other threads:[~2020-07-30 22:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 22:10 ro at gcc dot gnu.org [this message]
2020-07-30 22:11 ` [Bug d/96393] " ro at gcc dot gnu.org
2020-07-31  3:31 ` ro at gcc dot gnu.org
2020-07-31  7:31 ` jakub at gcc dot gnu.org
2020-07-31 10:07 ` ibuclaw at gdcproject dot org
2020-07-31 16:43 ` cvs-commit at gcc dot gnu.org
2020-07-31 16:48 ` ibuclaw at gdcproject dot 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-96393-4@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: 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).