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/109969] Linking large project causes an ICE Date: Thu, 07 Mar 2024 17:09:18 +0000 [thread overview] Message-ID: <bug-109969-4-nbNSpFyzfE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109969-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109969 --- Comment #2 from Gaius Mulley <gaius at gcc dot gnu.org> --- Created attachment 57647 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57647&action=edit Proposed fix Here is a proposed fix. The fix contains a re-write of M2LexBuf.mod which removes the linked list of token buckets and simplifies the implementation using a dynamic array. It contains more checking (for empty source files for example). The patch also contains a fix for an ICE in gcc/m2/gm2-gcc/builtins.cc - prompting this patch and potential commit once the bootstrap succeeds. Many of the test modules for this PR now compile. I've not seen the link occur as there are issues with the test Makefile.
next prev parent reply other threads:[~2024-03-07 17:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-25 17:43 [Bug modula2/109969] New: " gaius at gcc dot gnu.org 2023-05-25 17:46 ` [Bug modula2/109969] " gaius at gcc dot gnu.org 2024-03-07 17:09 ` gaius at gcc dot gnu.org [this message] 2024-03-07 19:42 ` cvs-commit at gcc dot gnu.org 2024-03-07 19:43 ` 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-109969-4-nbNSpFyzfE@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).