public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20983] [4.0 regression] varargs functions force va_list variable to stack unnecessarily
Date: Thu, 05 May 2005 17:13:00 -0000	[thread overview]
Message-ID: <20050505171107.32644.qmail@sourceware.org> (raw)
In-Reply-To: <20050413021014.20983.ian@airs.com>


------- Additional Comments From jakub at gcc dot gnu dot org  2005-05-05 17:11 -------
This could be fixed by expanding __builtin_va_start, __builtin_va_copy
and __builtin_va_end in or soon after pass_stdarg.
Then SRA etc. can also optimize va_list handling.
On the other side, tree-stdarg.c needs to see those builtins, otherwise it
won't be able to figure out anything.  Perhaps we can move that pass a little
bit earlier if needed, but it should certainly happen after at least DCE.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rth at gcc dot gnu dot org


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


  parent reply	other threads:[~2005-05-05 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13  2:10 [Bug c/20983] New: " ian at airs dot com
2005-04-13  3:26 ` [Bug c/20983] " ian at airs dot com
2005-04-13  4:45 ` [Bug middle-end/20983] " pinskia at gcc dot gnu dot org
2005-05-05 17:13 ` jakub at gcc dot gnu dot org [this message]
2005-09-24 17:18 ` [Bug middle-end/20983] [4.0/4.1regression] " pinskia at gcc dot gnu dot org
2005-09-27 16:08 ` mmitchel at gcc dot gnu dot org
2005-09-29  3:37 ` [Bug middle-end/20983] [4.0/4.1 Regression] " pinskia 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=20050505171107.32644.qmail@sourceware.org \
    --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).