bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] verify: avoid __builtin_assume
Date: Sun, 06 Sep 2020 10:46:39 +0200	[thread overview]
Message-ID: <1829268.qHUliUfUs6@omega> (raw)
In-Reply-To: <20200906005215.1179403-1-eggert@cs.ucla.edu>

Paul Eggert wrote:
> It’s not known whether
> the crash is due is a Clang bug or a portability bug in GNU Emacs.

Since around the time I added the __builtin_assume use in verify.h,
the gnulib integration test that Tim Rühsen maintains started to
occasionally fail - only in the clang/Debian run, not in the gcc/Debian
run. See <https://gitlab.com/gnulib/gnulib-ci/-/jobs>.

I say "around the time", since this integration test runs only once
a week.

I tried to reproduce locally, but couldn't - in my local build,
it succeeded.

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...

Bruno



  reply	other threads:[~2020-09-06  8:47 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 [this message]
2020-09-20 14:57   ` Bruno Haible
2020-09-20 17:23     ` Jim Meyering
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=1829268.qHUliUfUs6@omega \
    --to=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).