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/112408] [12/13/14 regression] d21 loops in getCpuInfo0B in Solaris/x86 kernel zone
Date: Tue, 07 Nov 2023 09:46:34 +0000 [thread overview]
Message-ID: <bug-112408-4-3Dy3xoJZDj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112408-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #3 from ibuclaw at gcc dot gnu.org ---
> Based on what I see here, this patch to core.cpuid should be sufficient to fix
> loop and not introduce any change in existing behaviour.
I've now bootstrapped a patched gcc 13.2.0 both inside the kernel zone
(amd64-pc-solaris2.11) and out, and indeed the build completes and there
are no differences in testsuite results between that run and an
equivalent one on bare metal.
One caveat, though: I originally used an unpatched gcc 11.4.0 as build
compiler. However, that doesn't work because the stage 1 d21 is linked
with the build compiler's libgphobos, thus loops when used. Applying
the patch to the gcc 11.4.0 sources and rebuilding fixed that.
Thanks a lot.
next prev parent reply other threads:[~2023-11-07 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 15:42 [Bug d/112408] New: " ro at gcc dot gnu.org
2023-11-06 15:42 ` [Bug d/112408] " ro at gcc dot gnu.org
2023-11-06 15:55 ` ibuclaw at gcc dot gnu.org
2023-11-06 15:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-06 17:07 ` ibuclaw at gcc dot gnu.org
2023-11-07 9:46 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2023-11-07 12:57 ` ibuclaw at gcc dot gnu.org
2023-11-07 13:00 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-07 13:19 ` ibuclaw at gcc dot gnu.org
2023-11-07 13:25 ` cvs-commit at gcc dot gnu.org
2023-11-07 13:26 ` cvs-commit at gcc dot gnu.org
2023-11-07 13:27 ` cvs-commit at gcc dot gnu.org
2024-02-02 20:41 ` ibuclaw at gdcproject dot 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-112408-4-3Dy3xoJZDj@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).