public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edlinger at gcc dot gnu.org" <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 21:04:20 +0000 [thread overview]
Message-ID: <bug-98225-4-PB6sekbHPL@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 #12 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Aah, now I see (lto-wrapper.c):
if (parallel)
{
fprintf (mstream, "%s:\n\t@%s ", output_name, new_argv[0]);
for (j = 1; new_argv[j] != NULL; ++j)
fprintf (mstream, " '%s'", new_argv[j]);
fprintf (mstream, "\n");
/* If we are not preserving the ltrans input files then
truncate them as soon as we have processed it. This
reduces temporary disk-space usage. */
if (! save_temps)
fprintf (mstream, "\t@-touch -r %s %s.tem > /dev/null 2>&1 "
"&& mv %s.tem %s\n",
input_name, input_name, input_name, input_name);
}
else
{
char argsuffix[sizeof (DUMPBASE_SUFFIX) + 1];
if (save_temps)
snprintf (argsuffix, sizeof (DUMPBASE_SUFFIX),
"ltrans%u.ltrans_args", i);
fork_execute (new_argv[0], CONST_CAST (char **, new_argv),
true, save_temps ? argsuffix : NULL);
maybe_unlink (input_name);
}
IF parallel is true, the "ltrans%u.ltrans_args and the "ltrans%u.ltrans_args.0
is obviously not taken.
AND on my system I use a gnu-make
that does not always pass the jobserver file ids to the sub-makes.
Only when "$(MAKE)" is used.
I already thought about adding something like "#$(MAKE)" somewhere
to un-break that....
next prev parent reply other threads:[~2021-01-06 21:04 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
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 [this message]
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-PB6sekbHPL@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).