public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65791] Postpone expand_ifn_va_arg till after optimize_va_list_gpr_fpr_size
Date: Fri, 17 Apr 2015 10:03:00 -0000 [thread overview]
Message-ID: <bug-65791-4-AbsaCLki4W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65791-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65791
vries at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-04-17
Ever confirmed|0 |1
--- Comment #1 from vries at gcc dot gnu.org ---
https://gcc.gnu.org/ml/gcc/2015-02/msg00115.html :
...
> [ We're still expanding ifn_va_arg before the va_list_gpr/fpr_size
> optimization. ]
Yeah, and the point of the exercise was of course to change that ;)
...
next prev parent reply other threads:[~2015-04-17 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 9:56 [Bug tree-optimization/65791] New: " vries at gcc dot gnu.org
2015-04-17 10:03 ` vries at gcc dot gnu.org [this message]
2015-04-29 9:41 ` [Bug tree-optimization/65791] " vries at gcc dot gnu.org
2015-05-11 11:15 ` vries at gcc dot gnu.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-65791-4-AbsaCLki4W@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).