https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
Thomas Koenig changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
--- Comment #11 from Thomas Koenig ---
> In this case a lot of informations are not necessary.
Those bug reporting guidelines are there for a reason:
To make it easier for developers (whose time is very
limited) to quickly reproduce bugs.
Witho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
--- Comment #10 from Helmut Schellong ---
(In reply to Thomas Koenig from comment #9)
> Please see https://gcc.gnu.org/bugs/#need for the things that
> are required for a bug report.
>
> Specifically,
>
> the preprocessed file (*.i*) that trig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
--- Comment #9 from Thomas Koenig ---
Please see https://gcc.gnu.org/bugs/#need for the things that
are required for a bug report.
Specifically,
the preprocessed file (*.i*) that triggers the bug, generated by adding
-save-temps to the complet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
--- Comment #8 from Helmut Schellong ---
Test case is a special measurement program.
See assembler code below:
strlen / repnz scasb
clock_gettime
gcc6 + gcc5
The exact gcc version is not critical.
Each gcc that injects an intel string instructio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
Thomas Koenig changed:
What|Removed |Added
Status|RESOLVED|WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27077
Helmut Schellong changed:
What|Removed |Added
CC||var at schellong dot biz
--- Comment
--- Comment #5 from rguenth at gcc dot gnu dot org 2008-01-26 12:37 ---
I think this benchmark is dubious, it likely depends on the library and
whatnot.
Also the benchmarks are out-of-date. Closing as invalid.
--
rguenth at gcc dot gnu dot org changed:
What|Removed
--- Comment #4 from hubicka at gcc dot gnu dot org 2006-08-08 06:35 ---
The strlen inlining depends on the -mtune switch. -mtune=athlon,generic and
i686
unrolls the strlen by in-line loop, while -mtune=pentium4 use the rep
operation.
Would be possible to benchmark both -mtune=generic an
--- Comment #3 from christophe dot jaillet at wanadoo dot fr 2006-06-01
21:37 ---
On my AMD Athlon and current HEAD and, I have other results, i.e. 2 or 3 times
FASTER :
(using your 19 bytes long 'aaa..' string)
stringfrom
lengthbuiltin library
(-O2)
--- Comment #2 from rdabrowa at poczta dot onet dot pl 2006-04-07 20:07
---
Execution times (in seconds) for different lengths:
stringfrom
lengthbuiltin library
--
0 0.480.07
5 0.570.11
100.65
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-04-07 19:12 ---
Your benchmark only deals with one sized strings, you should try with multiple
different sized strings like include one which is zero lengthed, one which is
2k-2M in length and try bechmarking that. You might get a
12 matches
Mail list logo
