public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105681] libstdc++-v3 fails to build on msp430 Date: Thu, 26 May 2022 20:59:21 +0000 [thread overview] Message-ID: <bug-105681-4-aUOGkyobge@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 #8 from Jonathan Wakely <redi at gcc dot gnu.org> --- And it was indeed something I asked for, see r12-2355 c++: Don't hide narrowing errors in system headers Jonathan pointed me at this issue where constexpr unsigned f() { constexpr int n = -1; return unsigned{n}; } is accepted in system headers, despite the narrowing conversion from a constant. I suspect that whereas narrowing warnings should be disabled, ill-formed narrowing of constants should be a hard error (which can still be disabled by -Wno-narrowing).
next prev parent reply other threads:[~2022-05-26 20:59 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 [this message] 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-aUOGkyobge@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).