GCC multi-version development layout

[Basile STARYNKEVITCH]

On Sun, 2026-04-19 at 17:14 +0000, Heime via Gcc-help wrote:
> On Sunday, April 19th, 2026 at 6:42 PM, Basile STARYNKEVITCH
> <basile@starynkevitch.net> wrote:
> 
> > On Sun, 2026-04-19 at 16:33 +0000, Heime via Gcc-help wrote:
> > > ----------------------------------------------------------------
> > > 
> > > When building GCC from a cloned Git source tree using separate
> > > directories (as recommended), the directory structure follows
> > > a clean separation of source, build artifacts, and final
> > > installation.
> > > 
> > > With different version of gcc, how would be the typical layout
> > > for specific branches to make patch changes to different gcc
> > > versions with multiple builds and install?
> > > 
> > > What are good books to read about version control useful for
> > > work on gcc branches.
> > 
> > 
> > I would suggest reading some good books on git
> 
> What would be a good book with many diagrams and examples?  
> And for reference?
>  

The book I own about git is: Pragmatic Guide To GIT
by Travis Swicegood ISBN 978-1-93435-672-1

there are probably many other ones see https://git-scm.com/

But on GCC you probably want to have your patches incorporated into
GCC.

On that I won't give good advices today (but see
https://arxiv.org/abs/1109.0779 ...)

And details are very specific (to rephrase your question: how to get
funded on GCC work, and what parts of GCC)

Thanks

-- 

Basile STARYNKEVITCH                           
<basile@starynkevitch.net>
8 rue de la Faïencerie                      
http://starynkevitch.net/Basile/  
92340 Bourg-la-Reine                        
https://github.com/bstarynk
France                               
https://github.com/RefPerSys/RefPerSys
                  https://orcid.org/0000-0003-0908-5250