public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 76857f1aae9af9d04ea401004f29c988a2593140 Date: Fri, 27 Oct 2023 21:08:33 +0000 (GMT) [thread overview] Message-ID: <20231027210833.DA5E4385B52D@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 76857f1aae9af9d04ea401004f29c988a2593140 (commit) from ccd0ad7343f217de53a755433329e384faa99339 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 76857f1aae9af9d04ea401004f29c988a2593140 Author: Sam James <sam@gentoo.org> Date: Fri Oct 27 22:07:15 2023 +0100 bugs: Mention -D_GLIBCXX_ASSERTIONS and -D_GLIBCXX_DEBUG These options both enable more checking within the C++ standard library and can expose errors in submitted code. -D_GLIBCXX_DEBUG is mentioned separately because while we want people to try it, it's not always feasible because it requires the whole program and any used libraries to also be built with it (as it breaks ABI). Signed-off-by: Sam James <sam@gentoo.org> diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index da3d4c0d..40355911 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -56,6 +56,14 @@ makes a difference, or if compiling with <code>-fsanitize=undefined</code> produces any run-time errors, then your code is probably not correct. </p> +<p>We also ask that for C++ code, users test their programs with +<code>-D_GLIBCXX_ASSERTIONS</code>. If you're able to rebuild the entire +program (including any libraries it uses, because it changes ABI), please do try +libstdc++'s <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/debug_mode.html">debug mode</a> +(<code>-D_GLIBCXX_DEBUG</code>) which enables more thorough checking in parts of +the C++ standard library. If either of these fail, this is a strong indicator +of an error in your code.</p> + <h2>Summarized bug reporting instructions</h2> <p>After this summary, you'll find detailed instructions that explain ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/index.html | 8 ++++++++ 1 file changed, 8 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-10-27 21:08 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231027210833.DA5E4385B52D@sourceware.org \ --to=redi@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.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: linkBe 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).