public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/97524] Compiling with -flto=auto fails in make is not installed
Date: Thu, 22 Oct 2020 07:22:06 +0000 [thread overview]
Message-ID: <bug-97524-4-5qQK6KcaRe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97524-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97524
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Well, can't it fall back to serial compilation?
It could, maybe with some diagnostic. It could also use fork-based
parallelism.
next prev parent reply other threads:[~2020-10-22 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 19:19 [Bug lto/97524] New: " tstellar at redhat dot com
2020-10-22 6:32 ` [Bug lto/97524] " marxin at gcc dot gnu.org
2020-10-22 7:15 ` jakub at gcc dot gnu.org
2020-10-22 7:22 ` rguenth at gcc dot gnu.org [this message]
2020-10-22 7:25 ` marxin at gcc dot gnu.org
2020-10-22 12:09 ` marxin at gcc dot gnu.org
2020-10-22 14:05 ` tstellar at redhat dot com
2020-10-23 7:03 ` marxin at gcc dot gnu.org
2020-10-23 7:48 ` cvs-commit at gcc dot gnu.org
2020-10-23 7:55 ` marxin 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-97524-4-5qQK6KcaRe@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).