From: Vladimir V <vv.os.swe@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Keith Packard <keithp@keithp.com>, libstdc++@gcc.gnu.org
Subject: Re: Problem building libstdc++ for the avr target
Date: Mon, 4 Jan 2021 12:28:31 +0100 [thread overview]
Message-ID: <CA+=iAiodYgB174_myTw5Oa9d91L4dzLstUhDO3n8TmYyk_69gA@mail.gmail.com> (raw)
In-Reply-To: <20201207210659.GK2309743@redhat.com>
Hello and Happy New Year!
Getting back to the discussion we had about scalable libstdc++.
For sure it will be very helpful for embedded targets. There are huge
components with
well defined boundaries that are unlikely to be often used in minimalist
settings but require missing platform support.
One particular example I'm looking at right now is 'filesystem'. Although
it resorts to some
default stubs if corresponding API is not present, I think it would be
correct to remove it from the library
completely if it can not/should not be used on the target.
In case of avr-libc it is worse as the unistd is partially present but not
sufficient to satisfy all filesystem
dependencies.
It looks like that after the filesystem support was implemented for c++17
standard there is no option to remove
it from the build (unlike for the filesystem-ts). Please correct me if I am
wrong but If it is like that I would like to make this configurable.
Would it be acceptable?
Thank you.
пн, 7 дек. 2020 г. в 22:07, Jonathan Wakely <jwakely@redhat.com>:
> On 07/12/20 12:41 -0800, Keith Packard via Libstdc++ wrote:
> >Jonathan Wakely via Libstdc++ <libstdc++@gcc.gnu.org> writes:
> >
> >>>and was resolved for the newlib. The fix was not applied for the
> avr-libc
> >>>targets although the rationale behind the solution
> >>>seems to be applicable there as well. I would like to ask what do you
> think
> >>>about extending the scope of the solution to work
> >>>with avr-libc based builds as well?
> >>
> >> Yes, I think it makes sense.
> >
> >I've been working on making libstdc++ work with picolibc, which shares a
> >bunch of stdio code with avr-libc. I haven't tried my patches with
> >avr-libc, but I wonder if that would be a good thing to do? With those
> >patches, I'm able to use libstdc++'s iostream.
>
> That might be interesting to try.
>
> I'm very much in favour of changes to libstdc++ that allow it to be
> used on small systems. While some C++ features may not be suitable for
> those systems, I think there's a lot of the standard library that is
> still useful, but isn't part of the current "freestanding" subset. And
> I'd like libstdc++ to be able to scale from very small to very large,
> rather than needing to fork it to meet those needs.
>
>
>
>
next prev parent reply other threads:[~2021-01-04 11:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 17:32 Vladimir V
2020-12-07 20:30 ` Jonathan Wakely
2020-12-07 20:32 ` Jonathan Wakely
2020-12-09 0:28 ` Vladimir V
2020-12-09 12:32 ` Vladimir V
2020-12-09 12:49 ` Jonathan Wakely
2020-12-09 17:01 ` Jonathan Wakely
2020-12-09 23:00 ` Vladimir V
2020-12-10 17:39 ` Vladimir V
2020-12-10 20:15 ` Jonathan Wakely
2020-12-10 20:31 ` Vladimir V
2020-12-15 11:48 ` Jonathan Wakely
2020-12-16 7:33 ` Vladimir V
2020-12-07 20:41 ` Keith Packard
2020-12-07 21:06 ` Jonathan Wakely
2021-01-04 11:28 ` Vladimir V [this message]
2021-01-08 18:21 ` Jonathan Wakely
2021-01-22 14:46 ` Vladimir V
2021-02-07 13:55 ` Vladimir V
2021-02-07 18:22 ` Vladimir V
2021-02-07 18:23 ` Keith Packard
2021-02-07 22:33 ` Vladimir V
2021-02-07 23:06 ` Keith Packard
2021-02-08 12:58 ` Vladimir V
2021-02-08 17:38 ` Jonathan Wakely
2021-02-08 17:45 ` Jonathan Wakely
2021-02-08 17:47 ` Jonathan Wakely
2021-02-08 22:25 ` Vladimir V
2021-02-09 10:47 ` Jonathan Wakely
2021-02-09 10:54 ` Vladimir V
2021-03-25 9:27 ` Vladimir V
2021-03-25 12:36 ` Jonathan Wakely
2021-03-25 18:27 ` Jonathan Wakely
2021-03-25 21:37 ` Vladimir V
2021-03-25 23:02 ` Jonathan Wakely
2021-03-26 8:25 ` Vladimir V
2020-12-07 21:51 ` Vladimir V
2020-12-07 23:00 ` Keith Packard
2020-12-08 8:12 ` Vladimir V
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='CA+=iAiodYgB174_myTw5Oa9d91L4dzLstUhDO3n8TmYyk_69gA@mail.gmail.com' \
--to=vv.os.swe@gmail.com \
--cc=jwakely@redhat.com \
--cc=keithp@keithp.com \
--cc=libstdc++@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).