public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Alexandre Oliva <oliva@adacore.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: testsuite: use -lbsd for net_ts on RTEMS
Date: Thu, 23 Jun 2022 10:06:48 +0100	[thread overview]
Message-ID: <CAH6eHdRK0S05CDM+hMS+FvPdw8h95OPgkuu1gz9xe0xOXXMrbA@mail.gmail.com> (raw)
In-Reply-To: <5e77936e-a80b-9df4-cc29-aa36cb301df6@embedded-brains.de>

On Thu, 23 Jun 2022, 10:02 Sebastian Huber, <
sebastian.huber@embedded-brains.de> wrote:

> On 22/06/2022 07:24, Alexandre Oliva via Gcc-patches wrote:
> > +    } elseif { [istarget *-*-rtems*] } {
> > +     # Adding -Wl,--gc-sections would enable a few more tests to
> > +     # link, but all of them fail at runtime anyway, because the
> > +     # io_context ctor calls pipe(), which always fails, and thus
> > +     # the ctor throws a system error.
> > +     return "$flags -lbsd"
>
> Using -Wl,--gc-sections is mandatory if you want to link against
> libbsd.a. In general, it is recommended for RTEMS applications.
>
> For pipe() support in RTEMS, you currently need the
>
> #define CONFIGURE_IMFS_ENABLE_MKFIFO
>
> application configuration option.
>


It would also be fine to just xfail the networking tests for rtems. Our
implementation of the Networking TS is incomplete, buggy, and unlikely to
evolve much until the C++ committee makes progress on standardized
networking.

Anybody who wants to use the Networking TS model has to use Boost.Asio for
real work, our partial implementation isn't good enough. So making it work
and pass tests on rtems isn't important.

  reply	other threads:[~2022-06-23  9:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  5:24 Alexandre Oliva
2022-06-22  9:11 ` Jonathan Wakely
2022-06-23  9:01 ` Sebastian Huber
2022-06-23  9:06   ` Jonathan Wakely [this message]
2022-06-23 11:26     ` Alexandre Oliva
2022-06-23 11:40       ` Jonathan Wakely
2022-06-23 12:39         ` Alexandre Oliva
2022-06-27 13:29           ` Alexandre Oliva

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=CAH6eHdRK0S05CDM+hMS+FvPdw8h95OPgkuu1gz9xe0xOXXMrbA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=oliva@adacore.com \
    --cc=sebastian.huber@embedded-brains.de \
    /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).