On 28.09.2020 10:59, Andriy Gapon wrote:
On 26/09/2020 22:55, Marek Zarychta wrote:
Thank you for the information and for the fix. Sadly I must admit it
doesn't work for me. I have tried two builds with fresh sources today to
be certain and it looks like the bug is still present on FreeBSD
13-CU
On 26/09/2020 22:55, Marek Zarychta wrote:
> Thank you for the information and for the fix. Sadly I must admit it
> doesn't work for me. I have tried two builds with fresh sources today to
> be certain and it looks like the bug is still present on FreeBSD
> 13-CURRENT r366186. Either the upstream f
On Sat, Sep 26, 2020 at 05:48:33PM +0200, Dimitry Andric wrote:
> On 26 Sep 2020, at 13:40, Marek Zarychta
> wrote:
> >
> > I have done a few builds of CURRENT in a row one or two weeks apart. The
> > builds with CPUTYPE?=amdfam10 set produce buggy code, for example while
> > running mergemaster
On 26 Sep 2020, at 13:40, Marek Zarychta wrote:
>
> I have done a few builds of CURRENT in a row one or two weeks apart. The
> builds with CPUTYPE?=amdfam10 set produce buggy code, for example while
> running mergemaster I get this error:
>
> PLEASE submit a bug report to https://bugs.freebsd.or
Dear list,
I have done a few builds of CURRENT in a row one or two weeks apart. The
builds with CPUTYPE?=amdfam10 set produce buggy code, for example while
running mergemaster I get this error:
PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and
include the crash backtrace, preproc
