public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/63971] Some of gcc.target/aarch64/test_frame_*.c tests fail now Date: Mon, 19 Jan 2015 12:58:00 -0000 [thread overview] Message-ID: <bug-63971-4-TYUi8NzO80@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63971-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63971 --- Comment #9 from Tejas Belagod <belagod at gcc dot gnu.org> --- Author: belagod Date: Mon Jan 19 12:57:48 2015 New Revision: 219838 URL: https://gcc.gnu.org/viewcvs?rev=219838&root=gcc&view=rev Log: 2015-01-19 Tejas Belagod <tejas.belagod@arm.com> PR target/63971 * gcc.target/aarch64/test_frame_1.c: Expect only two loads of x30 (in the epilogue). * gcc.target/aarch64/test_frame_6.c: Likewise. * gcc.target/aarch64/test_frame_2.c: Expect only one pair load of x30 and x19 (in the epilogue). * gcc.target/aarch64/test_frame_4.c: Likewise. * gcc.target/aarch64/test_frame_7.c: Likewise. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.target/aarch64/test_frame_1.c trunk/gcc/testsuite/gcc.target/aarch64/test_frame_2.c trunk/gcc/testsuite/gcc.target/aarch64/test_frame_4.c trunk/gcc/testsuite/gcc.target/aarch64/test_frame_6.c trunk/gcc/testsuite/gcc.target/aarch64/test_frame_7.c
next prev parent reply other threads:[~2015-01-19 12:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-19 17:22 [Bug testsuite/63971] New: " pinskia at gcc dot gnu.org 2014-11-22 23:42 ` [Bug testsuite/63971] " pinskia at gcc dot gnu.org 2015-01-09 16:59 ` pinskia at gcc dot gnu.org 2015-01-15 18:18 ` belagod at gcc dot gnu.org 2015-01-15 18:19 ` belagod at gcc dot gnu.org 2015-01-19 8:49 ` pinskia at gcc dot gnu.org 2015-01-19 12:58 ` belagod at gcc dot gnu.org [this message] 2015-10-29 23:22 ` mshawcroft 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-63971-4-TYUi8NzO80@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).