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/113768] gm2/extensions/run/pass/vararg2.mod FAILs
Date: Tue, 07 May 2024 18:57:50 +0000	[thread overview]
Message-ID: <bug-113768-4-GpnbHevbej@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113768-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:07dab3f6b56c711dcd737d856cf01a597a2e1626

commit r14-10179-g07dab3f6b56c711dcd737d856cf01a597a2e1626
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date:   Tue May 7 19:51:08 2024 +0100

    [PR modula2/113768][PR modula2/114133] bugfix constants must be cast prior
to vararg call

    This bug fix corrects the test codes below by converting the constant
    literals to the type required by C.  In the testcases below the values, 1
    etc were converted into the INTEGER type before being passed to a C
    vararg function.  By default in modula2 constant literal ordinals are
    represented as the ZTYPE (the largest GCC integer type node).

    gcc/testsuite/ChangeLog:

            PR modula2/113768
            PR modula2/114133
            * gm2/extensions/run/pass/callingc10.mod: Convert constant literal
            numbers into INTEGER.
            * gm2/extensions/run/pass/callingc11.mod: Ditto.
            * gm2/extensions/run/pass/vararg2.mod: Ditto.
            * gm2/iso/run/pass/packed.mod: Emit a printf as a runtime
            diagnostic.

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

  parent reply	other threads:[~2024-05-07 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 14:07 [Bug modula2/113768] New: " ro at gcc dot gnu.org
2024-02-05 14:07 ` [Bug modula2/113768] " ro at gcc dot gnu.org
2024-02-27 17:41 ` gaius at gcc dot gnu.org
2024-05-07  7:44 ` rguenth at gcc dot gnu.org
2024-05-07 18:57 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-07 18:58 ` 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-113768-4-GpnbHevbej@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).