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 libstdc++/105681] [12 Regression] libstdc++-v3 fails to build on msp430
Date: Wed, 08 Jun 2022 15:52:59 +0000 [thread overview]
Message-ID: <bug-105681-4-M1YsYcucEu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105681-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105681
--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:6666ca1ab44ad8a61e2b916cf4173fe452b78ed6
commit r12-8464-g6666ca1ab44ad8a61e2b916cf4173fe452b78ed6
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu May 26 21:32:55 2022 +0100
libstdc++: Fix narrowing conversions for 16-bit size_t [PR105681]
On a 16-bit target such as msp430 we get errors about narrowing long
values to size_t, which is only 16-bit. When --enable-libstdcxx-pch is
used the <bits/extc++.h> header breaks the build because of these
narrowing errors.
libstdc++-v3/ChangeLog:
PR libstdc++/105681
*
include/ext/pb_ds/detail/resize_policy/hash_prime_size_policy_imp.hpp:
Limit ga_sizes array to values that fit in size_t.
* include/ext/random [__SIZE_WIDTH < 32] (sfmt86243)
(sfmt86243_64, sfmt132049, sfmt132049_64, sfmt216091)
(sfmt216091_64): Do not declare.
(cherry picked from commit 367740bf6d3a6627798b3955e5d85efc7549ef50)
next prev parent reply other threads:[~2022-06-08 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 8:10 [Bug libstdc++/105681] New: " beagleboard at davidjohnsummers dot uk
2022-05-21 18:10 ` [Bug libstdc++/105681] " redi at gcc dot gnu.org
2022-05-22 9:01 ` beagleboard at davidjohnsummers dot uk
2022-05-22 16:05 ` mikpelinux at gmail dot com
2022-05-23 6:51 ` rguenth at gcc dot gnu.org
2022-05-26 20:04 ` beagleboard at davidjohnsummers dot uk
2022-05-26 20:24 ` redi at gcc dot gnu.org
2022-05-26 20:57 ` redi at gcc dot gnu.org
2022-05-26 20:59 ` redi at gcc dot gnu.org
2022-05-26 21:10 ` redi at gcc dot gnu.org
2022-05-26 21:31 ` cvs-commit at gcc dot gnu.org
2022-05-26 21:33 ` [Bug libstdc++/105681] [12 Regression] " redi at gcc dot gnu.org
2022-05-27 7:22 ` beagleboard at davidjohnsummers dot uk
2022-05-27 8:27 ` redi at gcc dot gnu.org
2022-06-08 15:52 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-08 16:10 ` redi 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-105681-4-M1YsYcucEu@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).