public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/112920] New: gm2 hangs in the type resolver
Date: Fri, 08 Dec 2023 13:54:08 +0000	[thread overview]
Message-ID: <bug-112920-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112920
           Summary: gm2 hangs in the type resolver
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: modula2
          Assignee: gaius at gcc dot gnu.org
          Reporter: gaius at gcc dot gnu.org
  Target Milestone: ---

Created attachment 56834
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56834&action=edit
test case showing bug

A large program with many data types causes gm2 to hang in the type resolver.

Forwarded from the gm2 mailing list to track bug progress etc:

"""
I could generate dynamic
or static binaries but now with version 191 gm2 seems to go into an
endless loop. Perhaps you can see what's going wrong?

BTW for staring a compilation one may simply enter

./mach_squash1

for a dynamic binary or

./mach_squash1_static

for a static binary in the relevant directory.
"""

It hangs in the dist_gm2_191 directory when invoked with:

$ gm2 -fiso -fsoft-check-all squash1.mod Ctv2.o unix.o -o squash1 -lc -lcrypt
-lm

             reply	other threads:[~2023-12-08 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 13:54 gaius at gcc dot gnu.org [this message]
2023-12-08 13:58 ` [Bug modula2/112920] " gaius at gcc dot gnu.org
2024-01-08 23:46 ` gaius at gcc dot gnu.org
2024-01-09 13:37 ` cvs-commit at gcc dot gnu.org
2024-01-09 14:01 ` gaius at gcc dot gnu.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-112920-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).