public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vda.linux at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/21182] gcc can use registers but uses stack instead
Date: Fri, 18 Jan 2013 00:51:00 -0000	[thread overview]
Message-ID: <bug-21182-4-poDWV40dXu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-21182-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21182

Denis Vlasenko <vda.linux at googlemail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vda.linux at googlemail dot
                   |                            |com

--- Comment #7 from Denis Vlasenko <vda.linux at googlemail dot com> 2013-01-18 00:51:01 UTC ---
"gcc-4.6.3 got better a bit, still not as good as gcc-4.6.3 -O3."

I meant:

gcc-4.6.3 got better a bit, still not as good as gcc-3.4.3 -O3 used to be.


  parent reply	other threads:[~2013-01-18  0:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21182-4@http.gcc.gnu.org/bugzilla/>
2013-01-18  0:48 ` vda.linux at googlemail dot com
2013-01-18  0:51 ` vda.linux at googlemail dot com [this message]
2013-01-18  0:55 ` vda.linux at googlemail dot com
2013-01-18  0:57 ` pinskia at gcc dot gnu.org
2013-01-18 10:39 ` [Bug rtl-optimization/21182] [4.6/4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2013-01-20 14:40 ` vda.linux at googlemail dot com
2013-03-13 20:38 ` steven at gcc dot gnu.org
2013-04-12 15:18 ` [Bug rtl-optimization/21182] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-06-12 13:49 ` [Bug rtl-optimization/21182] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:35 ` [Bug rtl-optimization/21182] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23  8:35 ` [Bug rtl-optimization/21182] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:03 ` [Bug rtl-optimization/21182] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:32 ` jakub at gcc dot gnu.org
2021-01-26 13:43 ` [Bug rtl-optimization/21182] [8/9/10/11 " rguenth at gcc dot gnu.org
2021-04-27 11:37 ` [Bug rtl-optimization/21182] [8/9/10/11/12 " jakub at gcc dot gnu.org
2021-07-28  7:04 ` [Bug rtl-optimization/21182] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-04-21  7:47 ` rguenth at gcc dot gnu.org
2023-05-29 10:01 ` [Bug rtl-optimization/21182] [10/11/12/13/14 " jakub at gcc dot gnu.org
2023-07-15  7:36 ` [Bug rtl-optimization/21182] [11/12/13/14 " pinskia at gcc dot gnu.org
2005-04-23 22:30 [Bug rtl-optimization/21182] New: " vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-23 22:32 ` [Bug rtl-optimization/21182] " vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-23 22:39 ` pinskia at gcc dot gnu dot org
2005-04-23 22:49 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-23 22:54 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-24 13:05 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-05-07 15:24 ` steven at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-21182-4-poDWV40dXu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).