On Mon, Oct 31, 2022 at 4:03 PM Jonathan Wakely
wrote:
>
> You've waited until two weeks before the deadline for GCC 13 changes!
> I'll re-propose my patch, but it would have been much better to do it
> when I wasn't rushing to get 20 *other* changes finished in the next
> two weeks!
Thank you,
On Sun, 30 Oct 2022 at 15:02, Baruch Burstein via Gcc wrote:
>
> On Tue, Feb 15, 2022 at 5:20 PM Jonathan Wakely
> wrote:
>
> >
> >
> > On Tue, 15 Feb 2022 at 13:58, David Malcolm wrote:
> >
> >> On Tue, 2022-02-15 at 12:55 +, Jonathan Wakely via Gcc wrote:
> >> > On Tue, 15 Feb 2022 at 12:3
On Tue, 15 Feb 2022 at 13:58, David Malcolm wrote:
> On Tue, 2022-02-15 at 12:55 +, Jonathan Wakely via Gcc wrote:
> > On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc <
> > gcc@gcc.gnu.org>
> > wrote:
> >
> > > Hi,
> > >
> > > I hope it is not inappropriate to call attention to a specif
On Tue, 2022-02-15 at 12:55 +, Jonathan Wakely via Gcc wrote:
> On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc <
> gcc@gcc.gnu.org>
> wrote:
>
> > Hi,
> >
> > I hope it is not inappropriate to call attention to a specific bug.
> > https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487.
>
On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc
wrote:
> Hi,
>
> I hope it is not inappropriate to call attention to a specific bug.
> https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487.
> I tried to do it myself, but got lost on the part where I needed to
> compile gcc 3 times and compare
