New branch for GC work - ReadList.com

1 msg	bug in g++ front-end
1 msg	gcc-4.3-20070914 is now available
2 msg	FW: Symbol Table Export From GCC?
5 msg	porting problem: segfault when compiling progra...
4 msg	Any chance for intel core --march?
3 msg	Stack parameter - pass by value - frame usage
1 msg	Work Online From Home.
29 msg	Is Sun putting much effort into supporting the ...
3 msg	Bootstrap broken - treelang: error: ‘treelang...
7 msg	GCC 4.3.0: Stage 3
3 msg	GCC 4.2 Branch Status: Slush

New branch for GC work
\ Laurynas Biveinis (11 Sep 2007)

3 msg	understanding __FUNCTION__ generation
2 msg	Recent (middle-end?) regressions in the Fortran...
4 msg	Polyhedron test: gas_dyn run-time performance r...
1 msg	support for float/complex math in libgcc cross-...
4 msg	SImode and PSImode question
1 msg	gcc-4.1-20070910 is now available
6 msg	deadline extension for debug info project into ...
9 msg	error compiling libgcc with ported cross-compiler

Subject:	New branch for GC work
Group:	Gcc
From:	Laurynas Biveinis
Date:	11 Sep 2007

Hello,

Since mainline is in, or is about to enter very soon, stage 3, I have
created a new branch "gc-improv" for GC work and related changes that
are not strictly bug fixes. The difference from the old boehm-gc
branch is that this one will not contain Boehm's GC integration.

As my previous email http://gcc.gnu.org/ml/gcc/2007-09/msg00144.html
did not receive any feedback, I assume that the plan there is OK and I
will proceed according to it:

- Take at least one more allocation site out of GC to pool or obstack;
- The "easy" parts of the last week's NEXT_INSN = NULL trainwreck;
- Couple more fixes/cleanups.
These will be submitted to mainline on stage1/stage2.

The interesting parts, already implemented in boehm-gc branch:
- gengtype changes to generate separate GC allocators for each used type
- convert GCC to use these
- add type-tags to objects

Then
- New GC marker, using type-tags.

I will document the gc-improv branch in svn.html shortly. Boehm-gc
will stay in the list of active branches until I finish porting over
stuff from it.

Any comments about the plan are still very welcome :)

--
Laurynas