[m-rev.] for review: announce workaround for GH issue #103

Mark Brown mark at mercurylang.org
Tue Jun 28 17:35:53 AEST 2022


Hi Julien,

This looks fine to me.

Mark

On Tue, Jun 28, 2022 at 4:19 PM Julien Fischer <jfischer at opturion.com> wrote:
>
>
> In the absence of any review comments, I will commit this one this
> evening.
>
> Julien.
>
> On Mon, 27 Jun 2022, Julien Fischer wrote:
>
> >
> > For review by anyone.
> >
> > ---------------------
> >
> > Announce the workaround for Github issue #103.
> >
> > NEWS:
> >     As above.
> >
> > Julien.
> >
> > diff --git a/NEWS b/NEWS
> > index bd3f762..3732d41 100644
> > --- a/NEWS
> > +++ b/NEWS
> > @@ -413,6 +413,15 @@ Changes to the extras distribution
> >
> > * We have deleted the `old_term_parser` library.
> >
> > +NEWS for Mercury 22.01.3
> > +========================
> > +
> > +This is a bug-fix release.
> > +
> > +* [Github issue #103]. We have disabled the use of some GCC optimizations
> > +  that were causing segmentation faults in code compiled in the `asm_fast`
> > +  grades with GCC versions 11 and 12 on x86_64 systems.
> > +
> >  NEWS for Mercury 22.01.2
> >  ========================
> >
> >
> >
> _______________________________________________
> reviews mailing list
> reviews at lists.mercurylang.org
> https://lists.mercurylang.org/listinfo/reviews


More information about the reviews mailing list