public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>, Paolo Bonzini <bonzini@gnu.org>,
	"Nathanael Nerode" <neroden@gcc.gnu.org>,
	Alexandre Oliva <aoliva@gcc.gnu.org>,
	"Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>
Subject: Document 'distclean-stage[N]'
Date: Wed, 26 Oct 2022 14:10:24 +0200	[thread overview]
Message-ID: <87h6zq4wgf.fsf@euler.schwinge.homeip.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 370 bytes --]

Hi!

OK to push the attached patch to "Document 'distclean-stage[N]'"?


Grüße
 Thomas


-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Document-distclean-stage-N.patch --]
[-- Type: text/x-diff, Size: 1796 bytes --]

From c20771b2fc13bdb24f3ad538c1806eeccbedfd3c Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Wed, 26 Oct 2022 13:07:27 +0200
Subject: [PATCH] Document 'distclean-stage[N]'

Refer to 'Makefile.tpl':

    # Rules to wipe a stage and all the following ones, also used for cleanstrap
    [+ IF prev +]distclean-stage[+prev+]:: distclean-stage[+id+] [+ ENDIF prev +]
    .PHONY: distclean-stage[+id+]
    distclean-stage[+id+]::
    	@: $(MAKE); $(stage)
    	@test "`cat stage_last`" != stage[+id+] || rm -f stage_last
    	rm -rf stage[+id+]-* [+
    	  IF compare-target +][+compare-target+] [+ ENDIF compare-target +]

	gcc/
	* doc/makefile.texi (Makefile Targets): Document
	'distclean-stage[N]'.
---
 gcc/doc/makefile.texi | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/gcc/doc/makefile.texi b/gcc/doc/makefile.texi
index fe0bbcd2ed1..5186c1cd9d5 100644
--- a/gcc/doc/makefile.texi
+++ b/gcc/doc/makefile.texi
@@ -135,6 +135,16 @@ Compares the results of stages 2 and 3.  This ensures that the compiler
 is running properly, since it should produce the same object files
 regardless of how it itself was compiled.
 
+@item distclean-stage@var{N} (@var{N} = 1@dots{}4, profile, feedback)
+Wipe stage @var{N} and all the following ones.
+
+For example,
+@samp{make distclean-stage3} wipes stage 3 and all the following ones,
+so that another @command{make} then rebuilds them from scratch.
+This can be useful if you're doing changes where
+``bubbling'' the changes as described above is not sufficient,
+but a full @command{make restrap} isn't necessary either.
+
 @item profiledbootstrap
 Builds a compiler with profiling feedback information.  In this case,
 the second and third stages are named @samp{profile} and @samp{feedback},
-- 
2.35.1


             reply	other threads:[~2022-10-26 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 12:10 Thomas Schwinge [this message]
2022-10-27 23:08 ` Jeff Law

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=87h6zq4wgf.fsf@euler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=aoliva@gcc.gnu.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=neroden@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: 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).