From: Jeff Law <law@redhat.com>
To: Honggyu Kim <hong.gyu.kim@lge.com>, gcc-patches@gcc.gnu.org
Cc: kyrylo.tkachov@arm.com, segher@kernel.crashing.org,
christophe.lyon@st.com
Subject: Re: [PATCH v2] New testcase to check parameter passing bug
Date: Wed, 25 Mar 2015 13:52:00 -0000 [thread overview]
Message-ID: <5512A9B1.1080104@redhat.com> (raw)
In-Reply-To: <1426729244-12509-1-git-send-email-hong.gyu.kim@lge.com>
On 03/18/15 19:40, Honggyu Kim wrote:
> Hi,
>
> I have modified the test-case to check parameter passing bug based on the
> comments from Kyrill Tkachov, Christophe Lyon, and Segher Boessenkool
> as follows:
> 1. move from "gcc.target/arm" to "gcc.dg"
> 2. change "dg-do compile" to "dg-do run"
>
> Please let me know if there's still something to fix more.
> Thanks for your comment.
>
> Honggyu
> ---
> gcc/testsuite/ChangeLog | 4 ++++
> gcc/testsuite/gcc.dg/pr65358.c | 33 +++++++++++++++++++++++++++++++++
> 2 files changed, 37 insertions(+)
> create mode 100644 gcc/testsuite/gcc.dg/pr65358.c
>
> diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
> index 77d24a1..218f908 100644
> --- a/gcc/testsuite/ChangeLog
> +++ b/gcc/testsuite/ChangeLog
> @@ -1,3 +1,7 @@
> +2015-03-19 Honggyu Kim <hong.gyu.kim@lge.com>
> +
> + * gcc.dg/pr65358.c: New test.
This should be included as part of Kyrill's patch. If the test goes in
without Kryill's fix, then it'll just create testsuite noise.
Jeff
next prev parent reply other threads:[~2015-03-25 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 2:08 [PATCH][ARM] " Honggyu Kim
2015-03-13 12:04 ` Kyrill Tkachov
2015-03-13 13:04 ` Christophe Lyon
2015-03-13 14:12 ` Segher Boessenkool
2015-03-16 0:54 ` Honggyu Kim
2015-03-18 11:53 ` Kyrill Tkachov
2015-03-19 1:40 ` [PATCH v2] " Honggyu Kim
2015-03-19 1:58 ` Honggyu Kim
2015-03-25 13:52 ` Jeff Law [this message]
2015-03-25 14:05 ` Kyrill Tkachov
2015-03-29 11:36 ` Honggyu Kim
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=5512A9B1.1080104@redhat.com \
--to=law@redhat.com \
--cc=christophe.lyon@st.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hong.gyu.kim@lge.com \
--cc=kyrylo.tkachov@arm.com \
--cc=segher@kernel.crashing.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).