From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-4.8: Move three links from http to https
Date: Sat, 5 Nov 2022 23:59:04 +0100 (CET) [thread overview]
Message-ID: <20221105225906.CC21733E18@hamza.pair.com> (raw)
Pushed.
Gerald
---
htdocs/gcc-4.8/changes.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/gcc-4.8/changes.html b/htdocs/gcc-4.8/changes.html
index 39557435..cb30a5e9 100644
--- a/htdocs/gcc-4.8/changes.html
+++ b/htdocs/gcc-4.8/changes.html
@@ -258,7 +258,7 @@ B b(42); // OK
</pre></blockquote>
</li>
- <li>As of GCC 4.8.1, G++ implements the change to <code>decltype</code> semantics from <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf">N3276</a>.
+ <li>As of GCC 4.8.1, G++ implements the change to <code>decltype</code> semantics from <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf">N3276</a>.
<blockquote><pre>
struct A f();
decltype(f()) g(); // OK, return type of f() is not required to be complete.
@@ -276,7 +276,7 @@ int i = A().f(); // error, f() requires an lvalue object
with features proposed for the next revision of the standard, expected
around 2014. Currently the only difference from <code>-std=c++11</code>
is support for return type deduction in normal functions, as proposed in
- <a href="http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2012/n3386.html">N3386</a>.
+ <a href="https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2012/n3386.html">N3386</a>.
Status of C++1y features in GCC 4.8 can be found <a href="../projects/cxx1y.html">here</a>.
</li>
@@ -436,7 +436,7 @@ int i = A().f(); // error, f() requires an lvalue object
gfortran's own array descriptor is used, which is different from the
one defined in TS29113, see <a
href="https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libgfortran/libgfortran.h">gfortran's header file</a> or use the <a
- href="http://chasm-interop.sourceforge.net/">Chasm Language
+ href="https://chasm-interop.sourceforge.net/">Chasm Language
Interoperability Tools</a>.</li>
</ul></li>
</ul>
--
2.38.0
reply other threads:[~2022-11-05 22:59 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=20221105225906.CC21733E18@hamza.pair.com \
--to=gerald@pfeifer.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).