grep-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [platform-testers] new snapshot available: grep-3.4-almost.19-ff30


From: Jim Meyering
Subject: Re: [platform-testers] new snapshot available: grep-3.4-almost.19-ff30
Date: Sat, 19 Sep 2020 08:22:05 -0700

On Thu, Sep 17, 2020 at 8:55 AM Nelson H. F. Beebe <beebe@math.utah.edu> wrote:
> At Utah, I can now report builds of grep-3.4-almost.19-ff30 on 279 systems,
> of which 251 report zero failures.  Here is a summary of the tests that
> failed:
>
>         alpine362       file
>         debian6b        pcre-invalid-utf8-input
>         slackware       pcre-invalid-utf8-input
>         netbsd81        reversed-range-endpoints
>         netbsd81        sjis-mb
>         midnightbsd10   stack-overflow
>         midnightbsd11   stack-overflow
>         midnightbsd12   stack-overflow
>         netbsd81        surrogate-pair
>         netbsd81        warn-char-classes
>         netbsd81        word-delim-multibyte
>
> Several builds on QEMU-emulated architectures are still in progress:
> they take 15x to 30x longer than native x86_64 builds.
>
> On Hipster OpenIndiana, I get this compilation failure with 
> CC=/opt/solarisstudio12.4/bin/cc:
>
>   CC       malloca.o
> "malloca.h", line 113: non-constant enumerator value
> "malloca.h", line 114: non-constant enumerator value
> "malloca.h", line 115: non-constant enumerator value
> "malloca.h", line 116: non-constant enumerator value
> cc: acomp failed for malloca.c
>
> On OpenMandriva Lx 4.1 (Mercury), with /usr/bin/cc == clang version 9.0.1,
> I get
>
>   CC       dfa.o
> In file included from dfa.c:61:
> ./xalloc.h:94:7: error: use of unknown builtin '__builtin_mul_overflow_p' 
> [-Wimplicit-function-declaration]
>   if (xalloc_oversized (n, s))
>       ^
> ./xalloc-oversized.h:46:4: note: expanded from macro 'xalloc_oversized'
>    __builtin_mul_overflow_p (n, s, (__xalloc_count_type) 1)
>    ^
> ... long cascade of similar errors ...

Hi Nelson,
Thank you for all the testing.
I'm hoping to have the time and means to investigate some of those.
Can you publish any of their test-suite.log files? That would make it
easy for others to investigate and sometimes even fix without
requiring access to such hosts.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]