public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20983] [4.0/4.1/4.2/4.3 Regression] varargs functions force va_list variable to stack unnecessarily
Date: Mon, 18 Jun 2007 06:55:00 -0000 [thread overview]
Message-ID: <20070618065520.26596.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20983-1313@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from pinskia at gcc dot gnu dot org 2007-06-18 06:55 -------
For -O1, it is even worse. I think we need to mark va_start/va_end as cannot
call clober their inputs at the tree level. This should at least fix the -O1
issue. It might also help code gen in other cases which I am not thinking of
currently.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20983
next prev parent reply other threads:[~2007-06-18 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20983-1313@http.gcc.gnu.org/bugzilla/>
2005-10-23 20:00 ` [Bug middle-end/20983] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-10-31 3:08 ` mmitchel at gcc dot gnu dot org
2006-02-24 0:26 ` [Bug middle-end/20983] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-04-18 14:16 ` bonzini at gnu dot org
2006-05-25 2:34 ` mmitchel at gcc dot gnu dot org
2006-08-26 1:27 ` kazu at gcc dot gnu dot org
2006-09-23 21:59 ` kazu at gcc dot gnu dot org
2007-02-14 9:05 ` [Bug middle-end/20983] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-06-18 6:55 ` pinskia at gcc dot gnu dot org [this message]
2007-11-15 17:42 ` jakub at gcc dot gnu dot org
2007-11-16 12:15 ` jakub at gcc dot gnu dot org
2007-12-06 13:26 ` jakub at gcc dot gnu dot org
2007-12-06 13:28 ` jakub at gcc dot gnu dot org
2007-12-06 16:55 ` rguenth 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=20070618065520.26596.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).