21 msgDynamically linking against GMP and MPFR
2 msgPR for multilib build problems?
2 msggcc 4.2 breaks debugging anonymous namespace
3 msgnamespace lookup
1 msggcc-4.2.0 for sparc64-linux and cygwin
1 msgGCC 3.4.6 to GCC 4.1.1 migration
2 msgFunction prologue - Debug info for frame relate...
1 msggcc-4.2-20070523 is now available
1 msgDataflow miscompiles soft-fp/floatuntitf.c on x...
2 msgThe best testsuite result on Linux/x86-64 in mo...
2 msgBOOT_CFLAGS and gcc trunk
1 msgDF branch benchmarking on SPEC2000
9 msggcc-current: badly worded warning?
1 msg[4.2.0] Can't bootstrap for cywin: bootstrap co...
5 msghttp://gcc.gnu.org/svn.html have a error.
2 msgGCC, Wei Chen wants to chat
1 msggcc-4.1-20070521 is now available

Volunteer for bug summaries?
\ Mark Mitchell (21 May 2007)
. \ Joe Buck (21 May 2007)
. \ Wei Chen (22 May 2007)
. \ Jan-Benedict Glaw (22 May 2007)
. . \ Manuel López-Ibáñez (22 May 2007)
. . . \ Jan-Benedict Glaw (22 May 2007)
. . . . \ Janis Johnson (22 May 2007)
. \ François-Xavier Coudert (22 May 2007)
. . \ Richard Guenther (22 May 2007)
. . . \ François-Xavier Coudert (22 May 2007)
. . . . \ Joe Buck (22 May 2007)
. . . . . \ François-Xavier Coudert (22 May 2007)
. . . . . \ Manuel López-Ibáñez (22 May 2007)
. . . . \ Andrew Pinski (23 May 2007)
. . . . \ Daniel Berlin (23 May 2007)
. . \ Ian Lance Taylor (22 May 2007)
. . . \ Mark Mitchell (23 May 2007)
. . . . \ Brooks Moses (23 May 2007)
. . . . . \ Joe Buck (23 May 2007)
. . . . . . \ Jan-Benedict Glaw (23 May 2007)
. . . . . . \ Rask Ingemann Lambertsen (28 May 2007)
. . . . \ Daniel Berlin (23 May 2007)
. . . . . \ Rask Ingemann Lambertsen (28 May 2007)
. . . . . . \ Daniel Berlin (28 May 2007)
. . . . . . . \ Joe Buck (29 May 2007)
. . . . . . . . \ Daniel Berlin (29 May 2007)
. . . . . \ Mark Mitchell (29 May 2007)
. . \ David Edelsohn (22 May 2007)
. \ Daniel Berlin (23 May 2007)

4 msghelp writing gcc code
4 msgProblem when using optimization on aix 5.2 and ...
Subject:Volunteer for bug summaries?
Group:Gcc
From:Mark Mitchell
Date:21 May 2007


I've received some feedback suggesting that some contributors may not
always be aware of what open issues are available to work on, and,
perhaps more importantly, what regressions they may have caused.

Is there a volunteer who would like to help prepare a regular list of
P3-and-higher PRs, together with -- where known -- the name of the
person responsible for the checkin which caused the regression? Or, is
this something that could be automated through Bugzilla, perhaps by
adding a pointer to the SVN revision at which the regression was introduced?

The goal would be to send a weekly/bi-weekly reminder to the list, and
to the responsible parties, to help remind those of us who've caused
problems to clean them up. I know that this would help me, both as a
developer and as the RM: as RM, it would help me see what's going on,
and as a developer, it would encourage me to clean up my messes, even
when I'm busy.

What do others think?

Thanks,

--
Mark Mitchell
CodeSourcery
mark
(650) 331-3385 x713


© 2004-2008 readlist.com