From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
Joseph Myers <joseph@codesourcery.com>,
Sandra Loosemore <sandra@codesourcery.com>
Subject: [wwwdocs] Suggest UBsan in https://gcc.gnu.org/bugs/
Date: Tue, 06 Oct 2015 10:54:00 -0000 [thread overview]
Message-ID: <20151006105401.GP12094@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
For many non-bugs UBsan is at least as likely to reveal it as
-fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations so we
should tell people to try that before wasting time in Bugzilla.
OK for wwwdocs?
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 873 bytes --]
Index: htdocs/bugs/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.116
diff -u -r1.116 index.html
--- htdocs/bugs/index.html 5 Jul 2014 21:52:32 -0000 1.116
+++ htdocs/bugs/index.html 6 Oct 2015 10:50:32 -0000
@@ -50,7 +50,11 @@
with <code>gcc -Wall -Wextra</code> and see whether this shows anything
wrong with your code. Similarly, if compiling with
<code>-fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations</code>
-makes a difference, your code probably is not correct.</p>
+makes a difference, your code probably is not correct.
+If compiling with <code>-fsanitize=undefined</code> is supported by your
+version of GCC and produces any run-time errors your code is definitely
+not correct.
+</p>
<h2>Summarized bug reporting instructions</h2>
next reply other threads:[~2015-10-06 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:54 Jonathan Wakely [this message]
2015-10-06 11:16 ` Jonathan Wakely
2015-10-07 14:18 ` Gerald Pfeifer
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=20151006105401.GP12094@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=joseph@codesourcery.com \
--cc=sandra@codesourcery.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.
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).