public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <yvan.roux@foss.st.com>, <ro@CeBiTec.Uni-Bielefeld.DE>,
	<mikestump@comcast.net>, <richard.sandiford@arm.com>
Subject: PING^1 [PATCH] testsuite: Do not prefix linker script with "-Wl,"
Date: Wed, 28 Sep 2022 11:18:19 +0200	[thread overview]
Message-ID: <3b573461-a954-cbf4-a805-24a4acf5a931@foss.st.com> (raw)
In-Reply-To: <20220919165735.4106606-1-torbjorn.svensson@foss.st.com>

Hi,

Ping: https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601831.html

Kind regards,
Torbjörn

On 2022-09-19 18:57, Torbjörn SVENSSON wrote:
> The linker script should not be prefixed with "-Wl," - it's not an
> input file and does not interfere with the new dump output filename
> strategy.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* lib/gcc-defs.exp: Do not prefix linker script with "-Wl,".
> 
> Signed-off-by: Torbjörn SVENSSON  <torbjorn.svensson@foss.st.com>
> ---
>   gcc/testsuite/lib/gcc-defs.exp | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gcc/testsuite/lib/gcc-defs.exp b/gcc/testsuite/lib/gcc-defs.exp
> index 42ef1d85432..2102ed6f7a3 100644
> --- a/gcc/testsuite/lib/gcc-defs.exp
> +++ b/gcc/testsuite/lib/gcc-defs.exp
> @@ -332,7 +332,7 @@ proc gcc_adjust_linker_flags_list { args } {
>   	    continue
>   	} elseif { $skip != "" } then {
>   	    set skip ""
> -	} elseif { $opt == "-Xlinker" } then {
> +	} elseif { $opt == "-Xlinker" || $opt == "-T" } then {
>   	    set skip $opt
>   	} elseif { ![string match "-*" $opt] \
>   		       && [file isfile $opt] } {

  reply	other threads:[~2022-09-28  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 16:57 Torbjörn SVENSSON
2022-09-28  9:18 ` Torbjorn SVENSSON [this message]
2022-09-28 14:08   ` PING^1 " Christophe Lyon
2022-09-30 16:19   ` Richard Sandiford

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=3b573461-a954-cbf4-a805-24a4acf5a931@foss.st.com \
    --to=torbjorn.svensson@foss.st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=richard.sandiford@arm.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=yvan.roux@foss.st.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).