From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][DOCS] Document make jobserver related changes for GCC 13.
Date: Thu, 18 Aug 2022 13:33:28 +0200 [thread overview]
Message-ID: <87f6f563-8e1a-0f14-8993-cc0bfb3d926c@suse.cz> (raw)
Ready for master?
---
htdocs/gcc-13/changes.html | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 57bd8724..95fee90d 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -52,6 +52,15 @@ a work-in-progress.</p>
AddressSanitizer defaults to <code>detect_stack_use_after_return=1</code> on GNU/Linux targets.
For compatibility, it can be disabled with <code>env ASAN_OPTIONS=detect_stack_use_after_return=0</code>.
</li>
+ <li>
+ Link-time optimization improvements:
+ <ul>
+ <li>LTO supports the newly added GNU make's jobserver that uses named pipes (<code>--jobserver-style=fifo</code>)
+ by default.</li>
+ <li>If make's jobserver is active, parallel LTO WPA streaming communicates with it and so the streaming
+ does not lead to the system overcommitting.</li>
+ </ul>
+ </li>
</ul>
--
2.37.1
next reply other threads:[~2022-08-18 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 11:33 Martin Liška [this message]
2022-08-18 20:53 ` Gerald Pfeifer
2022-08-22 9:24 ` Martin Liška
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=87f6f563-8e1a-0f14-8993-cc0bfb3d926c@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@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).