public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105681] libstdc++-v3 fails to build on msp430
Date: Sun, 22 May 2022 16:05:52 +0000	[thread overview]
Message-ID: <bug-105681-4-pOI3yajkNq@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

Mikael Pettersson <mikpelinux at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikpelinux at gmail dot com

--- Comment #3 from Mikael Pettersson <mikpelinux at gmail dot com> ---
I can reproduce in a cross to --target=msp430-unknown-elf
--enable-languages=c,c++ with binutils-2.38 and newlib-4.2.0.20211231.
gcc-11.3.0 builds fine, but gcc-12.1.0 build fails with

In file included from
/mnt/scratch/cross/sources/gcc-12.1.0/libstdc++-v3/include/precompiled/extc++.h:61:
/mnt/scratch/cross/objdir-gcc/msp430-unknown-elf/libstdc++-v3/include/ext/random:355:69:
error: narrowing conversion of '86243' from 'long int' to 'unsigned int'
[-Wnarrowing]
  355 |                                             0x00000000U, 0xe9528d85U>
      |                                                                     ^
(several more)

and

In file included from
/mnt/scratch/cross/objdir-gcc/msp430-unknown-elf/libstdc++-v3/include/ext/pb_ds/hash_policy.hpp:475,
                 from
/mnt/scratch/cross/objdir-gcc/msp430-unknown-elf/libstdc++-v3/include/ext/pb_ds/detail/standard_policies.hpp:45,
                 from
/mnt/scratch/cross/objdir-gcc/msp430-unknown-elf/libstdc++-v3/include/ext/pb_ds/assoc_container.hpp:47,
                 from
/mnt/scratch/cross/sources/gcc-12.1.0/libstdc++-v3/include/precompiled/extc++.h:72:
/mnt/scratch/cross/objdir-gcc/msp430-unknown-elf/libstdc++-v3/include/ext/pb_ds/detail/resize_policy/hash_prime_size_policy_imp.hpp:73:32:
error: narrowing conversion of '116731' from 'long unsigned int' to
'std::size_t' {aka 'unsigned int'} [-Wnarrowing]
   73 |       /* 14    */              116731ul,
      |                                ^~~~~~~~
(many more)

  parent reply	other threads:[~2022-05-22 16:05 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 [this message]
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
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-pOI3yajkNq@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).