From: Gary Oblock <gary@amperecomputing.com>
To: Toon Moene <toon@moene.org>, Erick Ochoa <eochoa@gcc.gnu.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Can gcc itself be tested with ubsan? If so, how?
Date: Wed, 29 Sep 2021 18:55:49 +0000 [thread overview]
Message-ID: <BYAPR01MB54642E389CA9FBF54CC87824C6A99@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <87a836f4-aeab-b0b0-39df-95c61becd723@moene.org>
Toon,
I assume the final compiler built this way has ubsan? I ask because
I'm trying to spot a bug in a new optimization so I want to
run it on a specific test case with the new optimization
enabled.
Thanks,
Gary
________________________________
From: Toon Moene <toon@moene.org>
Sent: Monday, September 27, 2021 11:47 PM
To: Erick Ochoa <eochoa@gcc.gnu.org>; Gary Oblock <gary@amperecomputing.com>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Re: Can gcc itself be tested with ubsan? If so, how?
[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]
On 9/28/21 8:35 AM, Erick Ochoa via Gcc wrote:
>> Can ubsan be used on the compiler itself?
I regularly build the compiler(s) natively with ubsan enabled, see for
instance:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-September/719448.html
The configure line tells you how to do it (towards the end of the mail):
configure flags: --prefix=/home/toon/compilers/install/gcc --with-gnu-as
--with-gnu-ld --enable-languages=all,ada --disable-multilib
--disable-nls --with-build-config=bootstrap-ubsan --enable-checking=all
(the enable-checking part is not relevant, and can be omitted).
Kind regards,
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
next prev parent reply other threads:[~2021-09-29 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 23:00 Gary Oblock
2021-09-28 6:35 ` Erick Ochoa
2021-09-28 6:47 ` Toon Moene
2021-09-28 10:53 ` Eric Gallager
2021-09-29 18:55 ` Gary Oblock [this message]
2021-10-01 20:11 ` Gary Oblock
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR01MB54642E389CA9FBF54CC87824C6A99@BYAPR01MB5464.prod.exchangelabs.com \
--to=gary@amperecomputing.com \
--cc=eochoa@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.org \
/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).