On 10 January 2011 16:08, Jeff Law wrote:
>
> But I think the key is to just keep the necessary builds hanging around,
> at least for the most popular targets.
The GCC Compile Farm has a number of releases installed under
/opt/cfarm/release/
See http://gcc.gnu.org/wiki/CompileFarm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/11 14:06, Tony Poppleton wrote:
> Thanks for the feedback.
>
>> Moving the test case into an attachment won't be useful. What would be
>> useful is recasting the test case into a form which can be used in the
>> gcc testsuite, if possible
>
Thanks for the feedback.
> Moving the test case into an attachment won't be useful. What would be
> useful is recasting the test case into a form which can be used in the
> gcc testsuite, if possible
Whilst I would like to be able to submit new test cases as I go, as
you (Ian) pointed out this m
On Thu, 6 Jan 2011, Ian Lance Taylor wrote:
> > 5. Similarly, if I mark a bug as known to work in 4.5.2, will this
> > lead to it eventually being closed?
>
> Yes, when the 4.4 release is closed, bugs known to work in 4.5 will be
> closed.
That's not how it works. I did the last couple of branc
On 7 January 2011 04:59, Tony Poppleton wrote:
> Hi,
>
> I would like to help with some gcc bug triage, and have a few
> questions about doing so.
Excellent, thanks for volunteering your time.
> For example, in cases where a bug doesn't have a test case as an
> attachmen
On Thu, Jan 06, 2011 at 10:31:28PM -0800, Ian Lance Taylor wrote:
> > 2. A large number of bugs seem to not be targetted for any particular
> > release, e.g. of the 4389 open bugs, only 296 are listed as targetted
> > for 4.6.0. Why is there such a discrepency?
> >
> > Incidentally, my main focus
Tony Poppleton writes:
> 1. My plan is to start testing bugs against the latest stable build
> (4.5.2), on an Intel x86-64 architecture (possibly also testing 32 bit
> bugs). My main focus will be on "missed-optimizations", although I
> will try and do others too. I have read the
> http://gcc.g
Hi,
I would like to help with some gcc bug triage, and have a few
questions about doing so.
1. My plan is to start testing bugs against the latest stable build
(4.5.2), on an Intel x86-64 architecture (possibly also testing 32 bit
bugs). My main focus will be on "missed-optimizations"