3 msggcc 4.2.2, libgomp under cygwin

PR1634: Request for gcc-cvs-patches list
\ Steven Bosscher (26 Nov 2007)
. \ Paolo Bonzini (26 Nov 2007)
. . \ Joseph S. Myers (26 Nov 2007)
. . . \ Daniel Berlin (27 Nov 2007)

6 msgIdea to refine -Wtype-limits
1 msgBounce Test
1 msg[Fwd: Libiberty problem in gcc-4.3 snapshots]
7 msg[RFC] [PATCH] 32-bit pointers in x86-64
8 msgRe: Designs for better debug info in GCC. Choic...
4 msgAutovectorizing HIRLAM; some progress.
3 msgInfinite loop when trying to bootstrap trunk
1 msggcc-4.3-20071123 is now available
1 msgStatus of GCC 4.3 on IA64 (Debian)
5 msg[Fwd: Re: FW: matrix linking]
8 msgDoes gcc support compiling for windows x86-64?
1 msgRiW k sLG
7 msg-Wconversion bug in g++-4.3?
5 msgSimple way to write almost same pattern?
2 msgunsatisfied link error
1 msggcc-4.2-20071121 is now available
2 msgStatus of GCC 4.3 on SPARC (Debian)
7 msgProblem with ARM_DOUBLEWORD_ALIGN on ARM
Subject:PR1634: Request for gcc-cvs-patches list
Group:Gcc
From:Steven Bosscher
Date:26 Nov 2007


Hello,

Back when God hadn't invented the dinosaurs yet (7 years ago) Joseph
opened a bug report requesting the creation of a gcc-cvs-patches
mailing list. The bug report can be found here:
http://gcc.gnu.org/PR1634.

Then, nothing happened for many years, a few comments aside.

Joseph wants to keep this bug report open to help "actively
remembering" people about this open issue, and to track this issue
over time. To me it seems there is nothing to track if no-one follows
up on te bug report. And with >4500 open bug report, I also don't see
how people are going to find this one simple requests. It is like a
needle in the hay stack, and nobody is even looking for the needle.

So I'm taking the issue here.

Do people think it is a good idea to have a gcc-cvs-patches list (or
gcc-svn-patches, also fine), where all patches automatically get sent
to, exactly as they are committed to SVN (maybe in gzip'ed form)?
This would have been especially useful before GCC started using SVN,
but even today there are some reasons to have this, as discussed in
the bug report.

Personally, I like the idea. But someone (probably Joseph, as the
requester) should persue the idea. If sufficient people thing this is
a good idea, we can think about how to implement it. Or the idea can
be rejected. In either case, the enhancement can finally be closed.

Gr.
Steven


© 2004-2008 readlist.com