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/66013] Missed optimization after inlining va_list parameter, -m32 case Date: Tue, 05 May 2015 07:34:00 -0000 [thread overview] Message-ID: <bug-66013-4-35JAHhm4FE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66013-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66013 --- Comment #2 from vries at gcc dot gnu.org --- And in the pass_stdarg dump, for f2 we see why the va_list escapes: ... va_list escapes in # .MEM_4 = VDEF <.MEM_2> apD.1830 = ap.0_3; ...
next prev parent reply other threads:[~2015-05-05 7:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-05 7:24 [Bug tree-optimization/66013] New: " vries at gcc dot gnu.org 2015-05-05 7:33 ` [Bug tree-optimization/66013] " vries at gcc dot gnu.org 2015-05-05 7:34 ` vries at gcc dot gnu.org [this message] 2015-05-05 7:41 ` vries at gcc dot gnu.org 2015-05-07 22:17 ` vries at gcc dot gnu.org 2015-05-08 15:37 ` vries at gcc dot gnu.org 2015-06-08 12:29 ` 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-66013-4-35JAHhm4FE@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: linkBe 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).