From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
Jason Merrill <jason@redhat.com>
Cc: Paolo Carlini <paolo.carlini@oracle.com>
Subject: [wwwdocs] Testing C++ changes (was: [patch] Make vector::at() assertion message more useful)
Date: Mon, 06 Apr 2015 11:37:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504061332430.9357@tuna.site> (raw)
In-Reply-To: <alpine.DEB.2.10.1309231542490.4526@stedding.saclay.inria.fr>
On Mon, 23 Sep 2013, Marc Glisse wrote:
> http://gcc.gnu.org/contribute.html has an outdated section on testing.
> It mentions that you should do a bootstrap for a change to the C
> front-end (should also be for the C++ front-end and I guess libstdc++
> even if it isn't used much inside gcc).
Somehow nobody bit or did update contribute.html anyway, so here
is a patch to adjust this.
Jason, any other thoughts?
Gerald
Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.85
diff -u -r1.85 contribute.html
--- contribute.html 27 Jun 2014 11:12:18 -0000 1.85
+++ contribute.html 6 Apr 2015 11:32:05 -0000
@@ -100,9 +100,9 @@
<h3>Which tests to perform</h3>
<p>If your change is to code that is not in a front end, or is to the
-C front end, you must perform a complete build of GCC and the runtime
-libraries included with it, on at least one target. You must
-bootstrap all default languages, not just C, and run all testsuites.
+C or C++ front ends, you must perform a complete build of GCC and the
+runtime libraries included with it, on at least one target. You must
+bootstrap all default languages, not just C and C++, and run all testsuites.
For a normal native configuration, running</p>
<blockquote><pre>
make bootstrap
@@ -111,17 +111,6 @@
<p>from the top level of the GCC tree (<strong>not</strong> the
<code>gcc</code> subdirectory) will accomplish this.</p>
-<p>If your change is to the C++ front end, you should rebuild the compiler,
-<code>libstdc++</code>, <code>libjava</code> and run the C++ testsuite.
-If you already did a complete C,C++,Java bootstrap from your build
-directory before, you can use the following:</p>
-<blockquote><pre>
-make clean-target-libstdc++-v3 # clean libstdc++ and ...
-test -d */libjava && make -C */libjava clean-nat # ... parts of libjava
-make all-target-libstdc++-v3 all-target-libjava # rebuild compiler and libraries
-make -k check-c++ # run C++/libstdc++ testsuite
-</pre></blockquote>
-
<p>If your change is to a front end other than the C or C++ front end,
or a runtime library other than <code>libgcc</code>, you need to verify
only that the runtime library for that language still builds and the
next prev parent reply other threads:[~2015-04-06 11:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 20:53 [patch] Make vector::at() assertion message more useful (try #2) Paul Pluzhnikov
2013-09-04 21:10 ` Daniel Krügler
2013-09-04 23:17 ` Paul Pluzhnikov
2013-09-05 4:55 ` Daniel Krügler
2013-09-13 5:19 ` Paul Pluzhnikov
2013-09-13 10:52 ` Paolo Carlini
2013-09-18 20:30 ` Paul Pluzhnikov
2013-09-18 23:24 ` Paolo Carlini
2013-09-22 10:19 ` Paul Pluzhnikov
2013-09-23 11:09 ` Andreas Schwab
2013-09-23 11:45 ` Paolo Carlini
2013-09-23 12:54 ` Richard Biener
2013-09-23 12:59 ` Andreas Schwab
2013-09-23 13:40 ` Paolo Carlini
2013-09-23 13:42 ` Andreas Schwab
2013-09-23 14:12 ` Paolo Carlini
2013-09-23 14:12 ` Marc Glisse
2013-09-23 14:12 ` Jakub Jelinek
2015-04-06 11:37 ` Gerald Pfeifer [this message]
2015-04-06 14:06 ` [wwwdocs] Testing C++ changes Jason Merrill
2013-09-23 15:18 ` [patch] Make vector::at() assertion message more useful (try #2) Paul Pluzhnikov
2013-09-23 15:26 ` Paolo Carlini
2013-09-23 16:38 ` Paul Pluzhnikov
2013-09-23 17:00 ` Paolo Carlini
2013-09-23 17:01 ` Paul Pluzhnikov
2013-09-23 16:21 ` Paul Pluzhnikov
2013-09-04 23:26 ` Paolo Carlini
2013-09-04 23:36 ` Paul Pluzhnikov
2013-09-04 23:44 ` Paolo Carlini
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=alpine.LSU.2.20.1504061332430.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).