public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/98225] gcc.misc-tests/outputs.exp ltrans_args tests FAIL
Date: Wed, 06 Jan 2021 10:50:21 +0000	[thread overview]
Message-ID: <bug-98225-4-BqLfyuey10@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98225-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> The arguments are in a response-file: @outputs.ld1_args
>> maybe that looks different for you?
>
> It certainly does (Solaris ld doesn't support -v, so no -Wl,-v here), as
> I found in collect2.c (do_link): the @ files are only passed if
> HAVE_GNU_LD and at_file_supplied.  The former is certainly false for
> Solaris ld, so we'll certainly see no outputs.ld1_args passed.

I've now dug a bit further and found two things: In addition to the
previous bootstraps with Solaris ld, I've run another one with GNU ld.
As expected, the outputs.ld1_args FAILs are gone since, unlike Solaris
ld, GNU ld *does* support response files.

On a hunch, I've also run

$ make -j2 check-gcc RUNTESTFLAGS=outputs.exp

(with gld in use, but this doesn't make a difference as I mentioned) and
lo, the previous FAILs now show up that didn't in a sequential make check-gcc.

  parent reply	other threads:[~2021-01-06 10:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 13:36 [Bug testsuite/98225] New: " ro at gcc dot gnu.org
2020-12-10 13:36 ` [Bug testsuite/98225] " ro at gcc dot gnu.org
2021-01-05 10:53 ` ro at gcc dot gnu.org
2021-01-05 18:20 ` edlinger at gcc dot gnu.org
2021-01-05 18:27 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-05 19:03 ` edlinger at gcc dot gnu.org
2021-01-05 19:24 ` burnus at gcc dot gnu.org
2021-01-05 19:40 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-05 19:57 ` edlinger at gcc dot gnu.org
2021-01-05 20:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-06 10:50 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2021-01-06 20:51 ` edlinger at gcc dot gnu.org
2021-01-06 21:00 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-06 21:04 ` edlinger at gcc dot gnu.org
2021-01-06 21:17 ` edlinger at gcc dot gnu.org
2021-01-06 21:22 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-07 18:52 ` dje at gcc dot gnu.org
2021-01-07 19:07 ` ro at gcc dot gnu.org
2021-01-07 19:41 ` edlinger at gcc dot gnu.org
2021-01-07 22:26 ` dje at gcc dot gnu.org
2021-01-11 12:29 ` cvs-commit at gcc dot gnu.org
2021-01-11 12:32 ` edlinger at gcc dot gnu.org

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-98225-4-BqLfyuey10@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).