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 modula2/113768] New: gm2/extensions/run/pass/vararg2.mod FAILs
Date: Mon, 05 Feb 2024 14:07:13 +0000 [thread overview]
Message-ID: <bug-113768-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113768
Bug ID: 113768
Summary: gm2/extensions/run/pass/vararg2.mod FAILs
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
Assignee: gaius at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Target: sparc*-sun-solaris2.11, s390x-ibm-linux-gnu,
m68k-unknown-linux-gnu
The gm2/extensions/run/pass/vararg2.mod test FAILs on Solaris/SPARC (32 and
64-bit) since its introduction:
FAIL: gm2/extensions/run/pass/vararg2.mod execution, -O
FAIL: gm2/extensions/run/pass/vararg2.mod execution, -O -g
FAIL: gm2/extensions/run/pass/vararg2.mod execution, -O3 -fomit-frame-pointer
FAIL: gm2/extensions/run/pass/vararg2.mod execution, -O3 -fomit-frame-pointer
-finline-functions
FAIL: gm2/extensions/run/pass/vararg2.mod execution, -Os
FAIL: gm2/extensions/run/pass/vararg2.mod execution, -g
There are also gcc-testresults reports for Linus/s390x and Linux/m68k.
On Solaris, the test prints
parameter is hello world and length 0
executed
/var/gcc/regression/master/11.4-gcc/build/gcc/testsuite/gm21/vararg2.x0 with
result fail
All affected targets are big-endian, though I don't yet see how this affects
the test.
next reply other threads:[~2024-02-05 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:07 ro at gcc dot gnu.org [this message]
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
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@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).