From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/2] Add some more test cases for fentry and pg
Date: Tue, 16 Sep 2014 18:00:00 -0000 [thread overview]
Message-ID: <CAMe9rOpcMyamzcqaJMiuOSHpCHBAmiWRj2X81Uxs7sUySbr-kw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqYzdzqCB7Xn0k7fR8s5eZeJNcUCS4G_aG28PhJh0XEhQ@mail.gmail.com>
On Tue, Sep 16, 2014 at 8:36 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Mon, Sep 15, 2014 at 8:59 AM, Andi Kleen <ak@linux.intel.com> wrote:
>> On Mon, Sep 15, 2014 at 11:29:50AM +0200, Richard Biener wrote:
>>> On Fri, Sep 12, 2014 at 4:32 PM, Andi Kleen <andi@firstfloor.org> wrote:
>>> > From: Andi Kleen <ak@linux.intel.com>
>>> >
>>> > Test fentry and no_instrument_function overriding.
>>> >
>>> > No test cases for the LTO test for now, as the LTO
>>> > harness doesn't seem to support different flags for the final
>>> > link.
>>>
>>> Sure it does - via dg-extra-ld-options (you have to negate compile-time
>>> opts to "remove" them).
>>
>> Ok. I'll add test cases for that too then.
>>
>>>
>>> Are you sure the tests are target independent enough? That is,
>>> 'mcount' is really 'mcount' on all targets?
>>
>> I'm not. I'll make them x86 only.
>>
>> Thanks,
>>
>> -Andi
>
> Tested on Linux/x86-64. I checked in this to fix:
>
> https://gcc.gnu.org/ml/gcc-regression/2014-09/msg00084.html
>
> --
> H.J.
> ---
> Index: ChangeLog
> ===================================================================
> --- ChangeLog (revision 215300)
> +++ ChangeLog (working copy)
> @@ -1,3 +1,7 @@
> +2014-09-16 H.J. Lu <hongjiu.lu@intel.com>
> +
> + * gcc.dg/pg.c: Fix a typo.
> +
> 2014-09-16 Richard Biener <rguenther@suse.de>
>
> PR testsuite/63258
> Index: gcc.dg/pg.c
> ===================================================================
> --- gcc.dg/pg.c (revision 215300)
> +++ gcc.dg/pg.c (working copy)
> @@ -1,6 +1,6 @@
> /* Test -fprofile override */
> /* { dg-do compile } */
> -/* { dg-options "-fprofile" { target { { i686-*-* x86_64-*-* } } } } */
> +/* { dg-options "-fprofile" { target i?86-*-* x86_64-*-* } } */
> /* { dg-final { scan-assembler-not "mcount" } } */
> /* Origin: Andi Kleen */
> extern void foobar(const char *);
Here is another one:
Index: ChangeLog
===================================================================
--- ChangeLog (revision 215303)
+++ ChangeLog (working copy)
@@ -1,5 +1,9 @@
2014-09-16 H.J. Lu <hongjiu.lu@intel.com>
+ * gcc.dg/pg-override.c: Fix a typo.
+
+2014-09-16 H.J. Lu <hongjiu.lu@intel.com>
+
* gcc.dg/pg.c: Fix a typo.
2014-09-16 Richard Biener <rguenther@suse.de>
Index: gcc.dg/pg-override.c
===================================================================
--- gcc.dg/pg-override.c (revision 215303)
+++ gcc.dg/pg-override.c (working copy)
@@ -1,6 +1,6 @@
/* Test -fprofile override */
/* { dg-do compile } */
-/* { dg-options "-fprofile" { target { { i686-*-* x86_64-*-* } } } } */
+/* { dg-options "-fprofile" { target i?86-*-* x86_64-*-* } } */
/* { dg-final { scan-assembler-not "mcount" } } */
/* Origin: Andi Kleen */
extern void foobar(const char *);
--
H.J.
next prev parent reply other threads:[~2014-09-16 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 14:33 [PATCH 1/2] Always set DECL_NO_INSTRUMENT_FUNCTION_ENTRY_EXIT correctly Andi Kleen
2014-09-12 14:33 ` [PATCH 2/2] Add some more test cases for fentry and pg Andi Kleen
2014-09-15 9:30 ` Richard Biener
2014-09-15 16:00 ` Andi Kleen
2014-09-16 15:37 ` H.J. Lu
2014-09-16 18:00 ` H.J. Lu [this message]
2014-09-15 9:28 ` [PATCH 1/2] Always set DECL_NO_INSTRUMENT_FUNCTION_ENTRY_EXIT correctly Richard Biener
2014-09-17 13:42 [PATCH 2/2] Add some more test cases for fentry and pg Dominique Dhumieres
2014-09-17 14:32 ` Andi Kleen
2014-09-17 14:39 ` Andi Kleen
2014-09-17 14:51 ` Jakub Jelinek
2014-09-17 15:46 ` Andi Kleen
2014-09-17 15:50 ` Jakub Jelinek
2014-09-17 16:19 ` Andi Kleen
2014-09-19 17:12 ` Andi Kleen
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=CAMe9rOpcMyamzcqaJMiuOSHpCHBAmiWRj2X81Uxs7sUySbr-kw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).