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++/107801] Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc) Date: Tue, 16 May 2023 12:50:47 +0000 [thread overview] Message-ID: <bug-107801-4-iaT4qon90F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107801-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:047c0fae82ca1458339e7e9724d125d30b685898 commit r11-10776-g047c0fae82ca1458339e7e9724d125d30b685898 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 22 09:53:36 2022 +0000 libstdc++: Fix pool resource build errors for H8 [PR107801] The array of pool sizes was previously adjusted to work for msp430-elf which has 16-bit int and either 16-bit size_t or 20-bit size_t. The largest pool sizes were disabled unless size_t has more than 20 bits. The H8 family has 16-bit int but 32-bit size_t, which means that the largest sizes are enabled, but 1<<15 produces a negative number that then cannot be narrowed to size_t. Replace the test for 32-bit size_t with a test for 32-bit int, which means we won't use the 4kiB to 4MiB pools for targets with 16-bit int even if they have a wider size_t. libstdc++-v3/ChangeLog: PR libstdc++/107801 * src/c++17/memory_resource.cc (pool_sizes): Disable large pools for targets with 16-bit int. (cherry picked from commit 0f9659e770304d3c44cfa0e793833a461bc487aa)
next prev parent reply other threads:[~2023-05-16 12:50 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-22 4:56 [Bug libstdc++/107801] New: " jdx at o2 dot pl 2022-11-22 9:08 ` [Bug libstdc++/107801] " redi at gcc dot gnu.org 2022-11-22 9:10 ` redi at gcc dot gnu.org 2022-11-22 9:20 ` redi at gcc dot gnu.org 2022-11-22 10:39 ` cvs-commit at gcc dot gnu.org 2022-11-22 11:06 ` cvs-commit at gcc dot gnu.org 2022-11-22 17:05 ` jdx at o2 dot pl 2022-11-22 17:09 ` redi at gcc dot gnu.org 2022-11-23 5:16 ` jdx at o2 dot pl 2022-11-26 21:41 ` pinskia at gcc dot gnu.org 2022-11-27 2:31 ` jdx at o2 dot pl 2022-11-27 7:35 ` redi at gcc dot gnu.org 2022-11-28 12:10 ` redi at gcc dot gnu.org 2022-11-28 13:32 ` redi at gcc dot gnu.org 2022-11-28 16:57 ` cvs-commit at gcc dot gnu.org 2022-11-28 17:01 ` redi at gcc dot gnu.org 2022-11-30 0:42 ` jdx at o2 dot pl 2022-11-30 1:48 ` redi at gcc dot gnu.org 2022-12-04 11:59 ` jdx at o2 dot pl 2023-05-16 12:50 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-16 15:37 ` cvs-commit at gcc dot gnu.org 2023-05-16 16:16 ` cvs-commit at gcc dot gnu.org 2023-05-16 16:17 ` 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-107801-4-iaT4qon90F@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: linkBe 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).