public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/114434] gdc.test/runnable/test23514.d FAILs
Date: Mon, 03 Jun 2024 07:47:29 +0000 [thread overview]
Message-ID: <bug-114434-4-94QdVRwGvM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114434-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114434
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #3 from Iain Buclaw <ibuclaw at gcc dot gnu.org> ---
> I see the test is pointer + 64-bit int. Is this UB on 32bit pointer platforms?
You're right: I only see the failure when d21 is a 32-bit binary; 64-bit
d21 is ok. However, both are supposed to work the same in multilibbed
configurations.
prev parent reply other threads:[~2024-06-03 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 15:26 [Bug d/114434] New: " ro at gcc dot gnu.org
2024-03-22 15:26 ` [Bug d/114434] " ro at gcc dot gnu.org
2024-03-22 15:35 ` ro at gcc dot gnu.org
2024-05-07 7:45 ` rguenth at gcc dot gnu.org
2024-06-02 12:49 ` ibuclaw at gcc dot gnu.org
2024-06-03 7:47 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
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-114434-4-94QdVRwGvM@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).