I've finally convinced myself that this patch is OK, because we
provide stub versions of all the functions being declared here. So if
a target is missing them, we provide them anyway. That happens to be
broken for the avr target, but that defaults to --disable-libstdcxx
anyway.
I've pushed the pat
On Wed, 17 May 2023 at 10:38, Nathaniel Shead
wrote:
> On Wed, May 17, 2023 at 10:05:59AM +0100, Jonathan Wakely wrote:
> > On Wed, 17 May 2023 at 09:37, Nathaniel Shead wrote:
> >
> > > Now that GCC13.1 is released is it ok to merge? Thanks!
> > >
> >
> > Yes, I've been testing this locally, but
On Wed, May 17, 2023 at 10:05:59AM +0100, Jonathan Wakely wrote:
> On Wed, 17 May 2023 at 09:37, Nathaniel Shead wrote:
>
> > Now that GCC13.1 is released is it ok to merge? Thanks!
> >
>
> Yes, I've been testing this locally, but I think it needs more work (sorry!)
>
> Looking at it again, I'm
On Wed, 17 May 2023 at 09:37, Nathaniel Shead wrote:
> Now that GCC13.1 is released is it ok to merge? Thanks!
>
Yes, I've been testing this locally, but I think it needs more work (sorry!)
Looking at it again, I'm not sure why I asked for the additional tests
because if they fail, it's a proble
Now that GCC13.1 is released is it ok to merge? Thanks!
On Tue, Apr 18, 2023 at 6:48 PM Jonathan Wakely wrote:
>
> On Mon, 17 Apr 2023 at 09:11, Nathaniel Shead
> wrote:
> >
> > Hi, just checking whether there were any issues with this patch?
> > https://gcc.gnu.org/pipermail/gcc-patches/2023-F
On Mon, 17 Apr 2023 at 09:11, Nathaniel Shead wrote:
>
> Hi, just checking whether there were any issues with this patch?
> https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612386.html
>
> Otherwise I assume it won't be in GCC13.
That's right, it's too large and invasive a change to get in
Hi, just checking whether there were any issues with this patch?
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612386.html
Otherwise I assume it won't be in GCC13.
Thanks,
Nathaniel
