[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21182 --- Comment #6 from Denis Vlasenko vda.linux at googlemail dot com 2013-01-18 00:48:23 UTC --- Created attachment 29200 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29200 Updated testcase, build heper, and results of testing with

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21182 Denis Vlasenko vda.linux at googlemail dot com changed: What|Removed |Added CC|

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21182 --- Comment #8 from Denis Vlasenko vda.linux at googlemail dot com 2013-01-18 00:55:37 UTC --- Grrr, another mistake. Correcting again: Conclusion: gcc-3.4.3 -O3 was close to ideal. ^ gcc-4.2.1 is worse. gcc-4.6.3 got better a

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21182 --- Comment #9 from Andrew Pinski pinskia at gcc dot gnu.org 2013-01-18 00:57:00 UTC --- It would be interesting to try the trunk which has a newer register allocator than even 4.6.x/4.7.x.

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

-- What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Last reconfirmed|-00-00 00:00:00

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

--- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-24 13:05 --- With 4.0.0: gcc -O2 gives the same result as gcc -O3, which is better than gcc 3.4.3 -O2 but worse than 3.4.3 -O3. For example: movl%edx, -20(%ebp) orl %ecx,

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

--- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-23 22:32 --- Created an attachment (id=8719) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8719action=view) testcase. change #if 0 into #if 1 and compare resulting asm --

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-23 22:39 --- Hmm, on the mainline, we get for wc -l: 1613 t.s 1459 t1.s t1 is the normal #if 0. Note I used -O2 -fomit-frame-pointer. -- What|Removed |Added

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

--- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-23 22:49 --- Aha! I found out that gcc will use registers with -O3, but not with -O2. # gcc -O3 serpent.c -S -o serpent-O3.s # gcc -O2 serpent.c -S -o serpent-O2.s # ls -l -rw-r--r-- 1 root root

[Bug rtl-optimization/21182] gcc can use registers but uses stack instead

--- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-23 22:54 --- These are -O2 and -O3 code comparison. -O3 code have all modified variables in registers and thus is smaller and most likely faster. serpent_encrypt: pushl %ebp