From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH][wwwdocs][obvious] Fix typo in -finline-matmul-limit
Date: Fri, 03 Jun 2016 08:26:00 -0000 [thread overview]
Message-ID: <57513F15.8090304@foss.arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 38 bytes --]
Committed as obvious.
Thanks,
Kyrill
[-- Attachment #2: wwwdocs-finline-limit.patch --]
[-- Type: text/x-patch, Size: 811 bytes --]
Index: htdocs/gcc-6/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.82
diff -U 3 -r1.82 changes.html
--- htdocs/gcc-6/changes.html 31 May 2016 08:01:35 -0000 1.82
+++ htdocs/gcc-6/changes.html 2 Jun 2016 10:21:18 -0000
@@ -346,7 +346,7 @@
cases if front-end optimization is active. The maximum size for
inlining can be set to <code>n</code> with the
<code>-finline-matmul-limit=n</code> option and turned off
- with <code>-finline-matmul-llimit=0</code>.</li>
+ with <code>-finline-matmul-limit=0</code>.</li>
<li>The <code>-Wconversion-extra</code> option will warn about
<code>REAL</code> constants which have excess precision for
their kind.</li>
reply other threads:[~2016-06-03 8:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57513F15.8090304@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--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).