public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "torbjorn.svensson at foss dot st.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/95720] [11 Regression] New dump output filename strategy invalidates tests
Date: Mon, 05 Sep 2022 18:29:56 +0000	[thread overview]
Message-ID: <bug-95720-4-oYjoZ6an5a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95720-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95720

Torbjörn SVENSSON <torbjorn.svensson at foss dot st.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |torbjorn.svensson at foss dot st.c
                   |                            |om

--- Comment #16 from Torbjörn SVENSSON <torbjorn.svensson at foss dot st.com> ---
I think this ticket should be reopened as the change broke how linker scripts
are handled in dejagnu.
If your board file have the following statement:

set_board_info ldscript "-T /path/to/foo.ld"

Then, the commands will be issued like this:

spawn -ignore SIGHUP .../build-native/gcc-final/gcc/xgcc
-B.../build-native/gcc-final/gcc/ linker_plugin9341.c -mthumb -march=armv6s-m
-mcpu=cortex-m0 -mfloat-abi=soft -fdiagnostics-plain-output -dumpbase  -flto
-fuse-linker-plugin -Wl,--start-group -lc -lm -Wl,--end-group
--specs=nosys.specs -Wl,--allow-multiple-definition -Wl,-u,_isatty,-u,_fstat
-Wl,-wrap,exit -Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -Wl,gcc_tg.o -lm
-T -Wl,/path/to/foo.ld -o linker_plugin9341.exe

Note that the ldscript symbol has been replaced by "-T -Wl,/path/to/foo.ld".
According to the manual, it's correct to have a white-space between -T and the
path.

  parent reply	other threads:[~2022-09-05 18:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 10:50 [Bug testsuite/95720] New: " akrl at gcc dot gnu.org
2020-06-17 10:53 ` [Bug testsuite/95720] [11 Regression] " rguenth at gcc dot gnu.org
2020-06-17 11:43 ` cvs-commit at gcc dot gnu.org
2020-06-24  6:39 ` aoliva at gcc dot gnu.org
2020-06-24 13:39 ` andrea.corallo at arm dot com
2020-06-24 19:23 ` aoliva at gcc dot gnu.org
2020-06-24 19:24 ` aoliva at gcc dot gnu.org
2020-06-24 19:45 ` aoliva at gcc dot gnu.org
2020-06-25  9:28 ` clyon at gcc dot gnu.org
2020-06-25 10:47 ` andrea.corallo at arm dot com
2020-07-16 23:15 ` aoliva at gcc dot gnu.org
2020-07-17 15:14 ` andrea.corallo at arm dot com
2020-07-17 18:51 ` aoliva at gcc dot gnu.org
2020-07-20  7:44 ` andrea.corallo at arm dot com
2020-07-24 19:16 ` cvs-commit at gcc dot gnu.org
2020-07-24 19:54 ` aoliva at gcc dot gnu.org
2022-09-05 18:29 ` torbjorn.svensson at foss dot st.com [this message]
2022-09-06  7:14 ` clyon at gcc dot gnu.org
2022-09-14  7:00 ` cvs-commit at gcc dot gnu.org
2022-10-03  5:17 ` torbjorn.svensson at foss dot st.com

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=bug-95720-4-oYjoZ6an5a@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).