From: Jim Meyering <jim@meyering.net>
To: Bruno Haible <bruno@clisp.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
"bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: Re: [PATCH] verify: avoid __builtin_assume
Date: Sun, 20 Sep 2020 10:23:33 -0700 [thread overview]
Message-ID: <CA+8g5KFfLckr96=VsxS1ZnppVq2W3Vf=D4CiR5Xd74XRckeb9g@mail.gmail.com> (raw)
In-Reply-To: <3870777.h6jr8M3dJ6@omega>
On Sun, Sep 20, 2020 at 7:59 AM Bruno Haible <bruno@clisp.org> wrote:
> On 2020-09-06 I wrote:
> > The actual failure is a
> > FAIL: test-regex
> > during "make check".
> >
> > Like Emacs, the regex code is quite complicated, so it is possible
> > that both the Emacs crash and the regex failure are caused by the
> > same clang bug.
> >
> > Let's see how the gnulib integration test will react to the revert...
>
> The gnulib integration test [1] is green in the last two builds. It looks
> like avoiding __builtin_assume fixed the test-regex failures with clang.
>
> Thanks, Paul. It saved me hours of investigation.
>
> Bruno
>
> [1] https://gitlab.com/gnulib/gnulib-ci/-/pipelines
Interested to see those tests, I visited your link, but for me it gets a 404.
Is there another way to get to the desired page?
next prev parent reply other threads:[~2020-09-20 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 0:52 [PATCH] verify: avoid __builtin_assume Paul Eggert
2020-09-06 8:46 ` Bruno Haible
2020-09-20 14:57 ` Bruno Haible
2020-09-20 17:23 ` Jim Meyering [this message]
2020-09-20 19:07 ` gnulib-ci project Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8g5KFfLckr96=VsxS1ZnppVq2W3Vf=D4CiR5Xd74XRckeb9g@mail.gmail.com' \
--to=jim@meyering.net \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).