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++/100285] experimental/net/socket/socket_base.cc fails on arm-eabi (r12-137)
Date: Fri, 09 Jun 2023 12:19:34 +0000	[thread overview]
Message-ID: <bug-100285-4-4g6g0nk9Ta@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100285-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100285

--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #12)
> This is failing for aarch64-none-elf:
> 
> FAIL: experimental/net/headers.cc (test for excess errors)

I hope this one is fixed on trunk now.

  parent reply	other threads:[~2023-06-09 12:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  9:53 [Bug libstdc++/100285] New: " clyon at gcc dot gnu.org
2021-04-27 13:09 ` [Bug libstdc++/100285] " cvs-commit at gcc dot gnu.org
2021-04-27 13:11 ` redi at gcc dot gnu.org
2021-04-30 12:23 ` clyon at gcc dot gnu.org
2021-04-30 13:47 ` cvs-commit at gcc dot gnu.org
2021-08-24 14:21 ` redi at gcc dot gnu.org
2021-08-24 16:00 ` cvs-commit at gcc dot gnu.org
2021-08-24 16:01 ` cvs-commit at gcc dot gnu.org
2021-08-25 16:20 ` clyon at gcc dot gnu.org
2021-08-26 11:44 ` cvs-commit at gcc dot gnu.org
2021-08-26 11:46 ` redi at gcc dot gnu.org
2021-10-12 19:41 ` cvs-commit at gcc dot gnu.org
2021-10-12 20:09 ` redi at gcc dot gnu.org
2021-10-13  8:17 ` clyon at gcc dot gnu.org
2023-06-09 12:18 ` cvs-commit at gcc dot gnu.org
2023-06-09 12:19 ` redi at gcc dot gnu.org [this message]
2023-06-29 23:01 ` cvs-commit at gcc dot gnu.org
2024-03-15 14:36 ` 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-100285-4-4g6g0nk9Ta@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).