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/64950] postpone expanding va_arg till pass_stdarg Date: Tue, 05 May 2015 10:38:00 -0000 [thread overview] Message-ID: <bug-64950-4-f56UtUpBWE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64950-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64950 --- Comment #13 from vries at gcc dot gnu.org --- Author: vries Date: Tue May 5 10:32:28 2015 New Revision: 222802 URL: https://gcc.gnu.org/viewcvs?rev=222802&root=gcc&view=rev Log: Xfail gcc.dg/tree-ssa/stdarg-2.c f15 scans 2015-05-05 Tom de Vries <tom@codesourcery.com> * gcc.dg/tree-ssa/stdarg-2.c: Xfail f15 scans which test for presence of 'va_list escapes 0'. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/tree-ssa/stdarg-2.c
next prev parent reply other threads:[~2015-05-05 10:38 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-05 17:05 [Bug tree-optimization/64950] New: " vries at gcc dot gnu.org 2015-02-22 15:27 ` [Bug tree-optimization/64950] " vries at gcc dot gnu.org 2015-02-24 12:50 ` vries at gcc dot gnu.org 2015-03-10 19:10 ` vries at gcc dot gnu.org 2015-04-16 8:51 ` vries at gcc dot gnu.org 2015-04-17 9:50 ` vries at gcc dot gnu.org 2015-04-17 9:51 ` vries at gcc dot gnu.org 2015-04-17 9:59 ` vries at gcc dot gnu.org 2015-04-17 12:53 ` ubizjak at gmail dot com 2015-04-17 14:09 ` vries at gcc dot gnu.org 2015-04-21 6:30 ` uros at gcc dot gnu.org 2015-05-04 13:10 ` ro at gcc dot gnu.org 2015-05-05 9:17 ` vries at gcc dot gnu.org 2015-05-05 10:38 ` vries at gcc dot gnu.org [this message] 2015-05-05 10:40 ` 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-64950-4-f56UtUpBWE@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).