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 d/112408] [12/13/14 regression] d21 loops in getCpuInfo0B in Solaris/x86 kernel zone
Date: Tue, 07 Nov 2023 13:27:40 +0000 [thread overview]
Message-ID: <bug-112408-4-9xp7JqPm1X@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 #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Iain Buclaw
<ibuclaw@gcc.gnu.org>:
https://gcc.gnu.org/g:47d833394a09068ba0607a57aa149dfe3dc11e8b
commit r11-11092-g47d833394a09068ba0607a57aa149dfe3dc11e8b
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date: Tue Nov 7 14:04:07 2023 +0100
libphobos: Fix regression d21 loops in getCpuInfo0B in Solaris/x86 kernel
zone
This function assumes that cpuid would return "invalid domain" when a
sub-leaf index greater than what's supported is requested. This turned
out not to always be the case when running on some virtual machines.
As the loop only does anything for levels 0 and 1, make that a hard
limit for number of times the loop is ran.
PR d/112408
libphobos/ChangeLog:
* libdruntime/core/cpuid.d (getCpuInfo0B): Limit number of times
loop
runs.
(cherry picked from commit 0b25c1295d4e84af681f4b1f4af2ad37cd270da3)
next prev parent reply other threads:[~2023-11-07 13:27 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
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 [this message]
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-9xp7JqPm1X@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).