From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 46847@debbugs.gnu.org, pipcet@gmail.com
Subject: bug#46847: 28.0.50; [native-comp] assume pseudo-insns should be verified
Date: Wed, 20 Mar 2024 15:05:40 +0200 [thread overview]
Message-ID: <86zfut2guz.fsf@gnu.org> (raw)
In-Reply-To: <yp1a5mttfmr.fsf@fencepost.gnu.org> (message from Andrea Corallo on Wed, 20 Mar 2024 05:30:04 -0400)
> Resent-To: bug-gnu-emacs@gnu.org
> Cc: 46847-done@debbugs.gnu.org, Pip Cet <pipcet@gmail.com>
> From: Andrea Corallo <acorallo@gnu.org>
> Date: Wed, 20 Mar 2024 05:30:04 -0400
>
> I'm closing this old bug as with 0b0c7da8c80 I've installed a sanitizer
> that instruments the code in order to check that compile time value
> predictions of mvars are respected at runtime. Mvars verified are all
> mvars being tested by conditional branches, this to verify the correct
> CFG/execution of the program.
>
> Enabling sanitizer instrumentation and runtime verification I'm able to
> bootstrap the compiler and run all the compiler testsuite.
>
> We might extend this further in the future but I think for now is okay.
Thanks, but would it be possible to document the suggested use of this
sanitizer in the comments somewhere?
next prev parent reply other threads:[~2024-03-20 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 13:06 bug#46847: 28.0.50; [native-comp] assume pseudo-insns should be verified Pip Cet
2021-03-01 20:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-02 6:57 ` Pip Cet
2021-03-05 11:16 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-05 16:09 ` Pip Cet
2021-03-05 19:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-14 21:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-20 9:30 ` Andrea Corallo
2024-03-20 13:05 ` Eli Zaretskii [this message]
2024-03-20 13:58 ` Andrea Corallo
2024-03-20 14:09 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zfut2guz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46847@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=pipcet@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).