public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/114418] Missing import of TSIZE from system causes ICE
Date: Thu, 21 Mar 2024 18:31:05 +0000	[thread overview]
Message-ID: <bug-114418-4-3Sq5SGiSKW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114418-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>:

https://gcc.gnu.org/g:ba744d50ac0360f7992a42494db766f6548913e3

commit r14-9598-gba744d50ac0360f7992a42494db766f6548913e3
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date:   Thu Mar 21 18:30:23 2024 +0000

    PR modula2/114418 missing import of TSIZE from system causes ICE

    This patch detects whether the symbol func is NulSym before generating
    an error and if so just uses the token location and fixed string to
    generate an error message.

    gcc/m2/ChangeLog:

            PR modula2/114418
            * gm2-compiler/PCSymBuild.mod (PushConstFunctionType): Check
            func against NulSym and issue an error.

    gcc/testsuite/ChangeLog:

            PR modula2/114418
            * gm2/pim/fail/missingtsize.mod: New test.
            * gm2/pim/fail/missingtsize2.mod: New test.

    Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>

  parent reply	other threads:[~2024-03-21 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 17:46 [Bug modula2/114418] New: " gaius at gcc dot gnu.org
2024-03-21 17:47 ` [Bug modula2/114418] " gaius at gcc dot gnu.org
2024-03-21 18:31 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-21 18:31 ` 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-114418-4-3Sq5SGiSKW@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).