public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/104019] Testsuite 17_intro/headers/c++2020/stdc++_multiple_inclusion.cc failures Date: Sat, 15 Jan 2022 08:58:22 +0000 [thread overview] Message-ID: <bug-104019-4-vutK43B1Aj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104019-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104019 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-01-15 Target| |*-*-freebsd* *-*-dragonfly* --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Oh there is a difference: include/bits/utility.h:#define __cpp_lib_integer_sequence 201304L include/std/version:# define __cpp_lib_integer_sequence 201304 include/std/utility:#define __cpp_lib_exchange_function 201304L include/std/version:# define __cpp_lib_exchange_function 201304 // FreeBSD wants warning clean system headers: // { dg-options "-Wall -Wsystem-headers" { target *-*-freebsd* *-*-dragonfly* } } Confirmed. I suspect there are more regressions lately because we have not had a testsuite results from dragonfly recently likewise from freebsd too.
next prev parent reply other threads:[~2022-01-15 8:58 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 6:06 [Bug libstdc++/104019] New: " rimvydas.jas at gmail dot com 2022-01-15 8:58 ` pinskia at gcc dot gnu.org [this message] 2022-01-15 9:36 ` [Bug libstdc++/104019] " redi at gcc dot gnu.org 2022-01-15 12:22 ` redi at gcc dot gnu.org 2022-01-15 12:23 ` redi at gcc dot gnu.org 2022-01-21 13:55 ` redi at gcc dot gnu.org 2022-01-21 16:08 ` cvs-commit at gcc dot gnu.org 2022-01-21 16:10 ` redi at gcc dot gnu.org 2022-01-23 22:49 ` cvs-commit at gcc dot gnu.org 2022-01-23 22:54 ` redi at gcc dot gnu.org 2022-01-24 5:57 ` rimvydas.jas at gmail dot com 2022-01-24 6:02 ` rimvydas.jas at gmail dot com 2022-01-24 12:23 ` redi at gcc dot gnu.org 2022-01-24 12:34 ` redi at gcc dot gnu.org 2022-01-25 21:09 ` cvs-commit at gcc dot gnu.org 2022-05-06 8:32 ` jakub at gcc dot gnu.org 2022-05-20 10:06 ` redi at gcc dot gnu.org 2023-05-08 12:23 ` rguenth 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-104019-4-vutK43B1Aj@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).