public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: Torsten Duwe <duwe@suse.de>
Cc: Andreas Schwab <schwab@suse.de>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	 GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] skip patchable_function_entry tests on ia64
Date: Mon, 14 Aug 2017 16:50:00 -0000	[thread overview]
Message-ID: <1502723397.12437.0.camel@tuliptree.org> (raw)
In-Reply-To: <20170811103429.5vmf4hlpox5abxnu@suse.de>

On Fri, 2017-08-11 at 12:34 +0200, Torsten Duwe wrote:
> gcc/testsuite/ChangeLog
> 2017-08-11  Torsten Duwe  <duwe@suse.de>
> 
> 	* c-c++-common/patchable_function_entry-default.c: Skip test on
> ia64.
> 	* c-c++-common/patchable_function_entry-decl.c: Likewise.
> 	* c-c++-common/patchable_function_entry-definition.c: Likewise.

OK.

Jim

      reply	other threads:[~2017-08-14 15:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 14:03 [PATCH v11] add -fpatchable-function-entry=N,M option Torsten Duwe
2017-07-07 13:58 ` Richard Earnshaw (lists)
2017-07-07 19:30   ` [PATCH v12] " Torsten Duwe
2017-07-17 12:10     ` Torsten Duwe
2017-07-20 10:58       ` Maxim Kuvyrkov
2017-07-20 12:06         ` Torsten Duwe
2017-07-20 13:12           ` Maxim Kuvyrkov
2017-07-25  7:16             ` Maxim Kuvyrkov
2017-07-25  8:07               ` Torsten Duwe
2017-07-25 13:03               ` Torsten Duwe
2017-07-26 14:16     ` Andreas Schwab
2017-07-26 14:26       ` Torsten Duwe
2017-07-26 14:33         ` Andreas Schwab
2017-07-31 11:47           ` Maxim Kuvyrkov
2017-08-01 10:43             ` Gerald Pfeifer
2017-08-01 10:53               ` Andreas Schwab
2017-08-01 13:03                 ` Maxim Kuvyrkov
2017-08-01 13:36                   ` Andreas Schwab
2017-08-11 12:42                   ` [PATCH] skip patchable_function_entry tests on ia64 Torsten Duwe
2017-08-14 16:50                     ` Jim Wilson [this message]

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=1502723397.12437.0.camel@tuliptree.org \
    --to=wilson@tuliptree.org \
    --cc=duwe@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=schwab@suse.de \
    /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).