public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Toma Tabacu <Toma.Tabacu@imgtec.com>
Cc: Renlin Li <renlin.li@foss.arm.com>,
	       "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       Matthew Fortune <Matthew.Fortune@imgtec.com>,
	       "catherine_moore\@mentor.com" <catherine_moore@mentor.com>
Subject: Re: [PATCH,testsuite] Add check_effective_target_rdynamic and use it in g++.dg/lto/pr69589_0.C.
Date: Tue, 06 Jun 2017 10:02:00 -0000	[thread overview]
Message-ID: <yddy3t5bfi9.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <A614194ED15B4844BC4C9FB7F21FCD9270474D5A@hhmail02.hh.imgtec.org>	(Toma Tabacu's message of "Mon, 5 Jun 2017 12:21:01 +0000")

Hi Toma,

>> Thanks for fixing this! Do you have plan to backport the fix to gcc-6 branch?
>
> I am happy to backport it.
> I've rebased the patch on top of the gcc-6 branch and attached it below.
>
> Rainer, is this OK for gcc-6?

sure, thanks.

	Rainer


> gcc/ChangeLog:
>
> 	Backported from mainline
> 	2017-03-09  Toma Tabacu  <toma.tabacu@imgtec.com>
>
> 	* doc/sourcebuild.texi (Effective-Target Keywords, Other attributes):
> 	Document rdynamic.
>
> gcc/testsuite/ChangeLog:
>
> 	Backported from mainline
> 	2017-03-09  Toma Tabacu  <toma.tabacu@imgtec.com>
>
> 	* g++.dg/lto/pr69589_0.C: Add dg-require-effective-target for
> 	rdynamic.
> 	* lib/target-supports.exp (check_effective_target_rdynamic):
> 	New proc.

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2017-06-06 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 14:17 Toma Tabacu
2017-03-08 15:04 ` Rainer Orth
2017-03-09  9:39   ` Matthew Fortune
2017-03-09 15:08   ` Toma Tabacu
2017-06-02 14:06     ` Renlin Li
2017-06-05 12:21       ` Toma Tabacu
2017-06-06 10:02         ` Rainer Orth [this message]
2017-06-06 11:55           ` Toma Tabacu

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=yddy3t5bfi9.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=Toma.Tabacu@imgtec.com \
    --cc=catherine_moore@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=renlin.li@foss.arm.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).