Hi,
The following article has a fairly comprehensive set of benchmarks run
against all the current stable releases of GCC as well as 4.6.0.
http://www.phoronix.com/scan.php?page=articleitem=intel_avx_gccnum=1
There are some great results for 4.6.0 in there, which is very good
news
While I appreciate Phoronix as a booster site, their benchmarking
practice often seems very dodgy; I'd take the results with a large grain
of salt
The main reason I posted the link in the first place was because it
was reflecting my own emperical evidence for the application I am
working
Could someone with the powers please modify my permissions to the above?
I will do that if a gcc maintainer vouches for you.
For the record, this situation has now been resolved and I can edit
the bugs as requested.
Many thanks,
Tony
Hi,
On Wed, Jan 26, 2011 at 2:36 PM, Richard Guenther
richard.guent...@gmail.com wrote:
I have added you to the reconfirmers group, please check if that makes
it work.
Thanks, however I am still unable to make the changes in bugzilla, specifically;
- modify known to fail/known to work fields
Hi,
I am working on some GCC bug triage, and am unable to edit the known
to fail/work fields in Bugzilla, as well as modify the status of a
bug.
On the overseers list, Ian Lance Taylor suggested I post to this list
requesting a gnu.gcc.org email account, as they come with all the
necessary
, Jan 26, 2011 at 3:32 PM, Tony Poppleton
tony.popple...@gmail.com wrote:
Hi,
I am working on some GCC bug triage, and am unable to edit the known
to fail/work fields in Bugzilla, as well as modify the status of a
bug.
On the overseers list, Ian Lance Taylor suggested I post to this list
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 may
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, although I
