public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/104911] [12 regression] Comparison failure in gcc/d/typesem.o etc.
Date: Fri, 18 Mar 2022 09:45:14 +0000 [thread overview]
Message-ID: <bug-104911-4-PExpXW5NnV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104911-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104911
--- Comment #6 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Created attachment 52649
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52649&action=edit
fdump-tree-original
The corrupt is indeed coming from the front-end.
Attached tree dumps.
--- stage2/typesem.d.005t.original 2022-03-18 10:40:44.087366215 +0100
+++ stage3/typesem.d.005t.original 2022-03-18 10:41:11.776070215 +0100
@@ -2994,7 +2994,7 @@ struct Expression * visitBasic (const st
switch ((int) __frame.mt->ty)
{
case 13:;
- return <retval> = integerValue (&__frame, 18446744073709551488);
+ return <retval> = integerValue (&__frame, 128);
case 14:;
case 16:;
case 18:;
next prev parent reply other threads:[~2022-03-18 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 10:43 [Bug d/104911] New: " ro at gcc dot gnu.org
2022-03-14 10:44 ` [Bug d/104911] " ro at gcc dot gnu.org
2022-03-14 10:45 ` ro at gcc dot gnu.org
2022-03-14 18:26 ` ibuclaw at gdcproject dot org
2022-03-14 21:16 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-15 11:39 ` ro at gcc dot gnu.org
2022-03-15 14:07 ` ibuclaw at gdcproject dot org
2022-03-18 9:45 ` ibuclaw at gdcproject dot org [this message]
2022-03-18 10:21 ` ibuclaw at gdcproject dot org
2022-03-21 19:56 ` cvs-commit at gcc dot gnu.org
2022-03-21 19:59 ` ibuclaw at gdcproject dot org
2022-03-23 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-104911-4-PExpXW5NnV@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).