This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Just checking - which branch
- From: Tim Josling <tej at melbpc dot org dot au>
- To: gcc-patches at gcc dot gnu dot org
- Date: Sat, 04 May 2002 10:17:22 +1000
- Subject: Just checking - which branch
- Organization: Melbourne PC User Group
I have been threatening to apply my treelang patch for some time, but
before I do I just want to make sure exactly which branch to check it
into.
Here are the current branches
"MAIN/default"
gcc_latest_snapshot
gcc_ss_yyyymmdd
gcc-3_1-branch
gcc_3_0_4_release
gcc_3_0_3_release
gcc_3_0_2_release
gcc_3_0_1_release
gcc_3_0_release
gcc-3_0-branch
gcc-2_95_3
gcc-2_95_2-release
gcc-2_95_1-release
gcc-2_95-release
gcc-2_95-branch
gnu-win32-b20-branch
dfa-branch. This branch contains the insn scheduler with an automaton
based pipeline hazard recognizer.
cfg-branch
ast-optimizer-branch
x86-64-branch.
pch-branch.
It appears that gcc_latest_snapshot is the latest version of gcc3.1,
gcc_ss_yyymmdd is a weekly snapshot of whatever is the current
production branch (at present gcc3.1).
It also appears that MAIN is what will turn into gcc3.2. The last five
branches in the list are specialised for various optimisation/cpu
support projects, the *-win32-b20 branch is for win32 and the others are
basically historical.
My thinking is that I would patch to the main/default/non-branch (gcc3.2
experimental). This is the one that will turn into gcc3.2. Then I can
track gcc3.2 from there.
So treelang would be in gcc3.2 but not any earlier release. The other
alternative would be to put it in gcc-3.1-branch which is according to
me the current gcc3.1 bleeding edge.
If I have gotten this wrong could someone please let me know.
Assuming this is right I will need to make some updates as someone has
revamped the langhooks again.
Tim Josling