From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: Replace reference to gccupc.org with the new site on Github.
Date: Sun, 20 Sep 2020 16:22:14 +0200 (CEST) [thread overview]
Message-ID: <20200920142243.A5ABE33E1E@hamza.pair.com> (raw)
Also shorten some text, call GCC that instead of GNU GCC compiler,
and remove some bits and links where there appears no equivalent
available on that new site.
Pushed.
Gerald
---
htdocs/frontends.html | 2 +-
htdocs/git.html | 2 +-
htdocs/projects/gupc.html | 33 +++++++--------------------------
3 files changed, 9 insertions(+), 28 deletions(-)
diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index 2d996cbd..bec33b7b 100644
--- a/htdocs/frontends.html
+++ b/htdocs/frontends.html
@@ -64,7 +64,7 @@ Currently they only support GNU/Linux x86 systems.</li>
<li><a href="http://pl1gcc.sourceforge.net/">PL/1 for GCC</a> is a
GCC front end for the PL/I language.</li>
-<li><a href="http://www.gccupc.org/">GCC Unified Parallel C</a>
+<li><a href="https://github.com/Intrepid/GUPC">GCC Unified Parallel C</a>
(GCC UPC) is a compilation and execution environment for Unified
Parallel C.</li>
</ul>
diff --git a/htdocs/git.html b/htdocs/git.html
index 905ce80e..96a921df 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -478,7 +478,7 @@ in Git.</p>
high-performance, parallel systems with access to a single
potentially large, global shared address space.
Further information can be found on the
- <a href="http://gccupc.org">GNU UPC</a> web page.</dd>
+ <a href="https://github.com/Intrepid/GUPC">GNU UPC</a> page.</dd>
<dt>pph</dt>
<dd>This branch implements <a href="https://gcc.gnu.org/wiki/pph"> Pre-Parsed
diff --git a/htdocs/projects/gupc.html b/htdocs/projects/gupc.html
index 3b822ca3..0c55c571 100644
--- a/htdocs/projects/gupc.html
+++ b/htdocs/projects/gupc.html
@@ -16,11 +16,10 @@
<p>The GNU UPC project implements a compilation and execution environment for
programs written in the
-<a href="https://www.gccupc.org">UPC (Unified Parallel C)</a> language.
-The GNU UPC compiler extends the capabilities of the
-GNU GCC compiler. The GUPC compiler is
-implemented as a C Language dialect translator, in a fashion similar to the
-implementation of the GNU Objective C compiler.
+<a href="https://github.com/Intrepid/GUPC">UPC (Unified Parallel C)</a>
+language. The GNU UPC compiler extends the capabilities of GCC.
+The GUPC compiler is implemented as a C Language dialect translator, in
+a fashion similar to the implementation of the GNU Objective C compiler.
</p>
<h2>Project Goal</h2>
@@ -79,29 +78,11 @@ on a platform of interest to you, we recommend that you join the
<h2>Download</h2>
-<p>The latest release of GUPC can be downloaded from <a
-href="https://www.gccupc.org/download">gccupc.org</a>.
-</p>
-
-<p>Alternatively, read-only SVN access to the GUPC branch can be used to
-acquire the latest development source tree:
-</p>
-
-<pre>svn checkout svn://gcc.gnu.org/svn/gcc/branches/gupc</pre>
+<p>The <a href="https://github.com/Intrepid/GUPC/releases">latest
+release</a> of GUPC is available for download.</p>
-<h2>Documentation</h2>
+<p>Alternatively, you can access the GUPC branch in the GCC sources.</p>
-<p>For a list of configuration switches that you can use to build GUPC, consult
-the GUPC
-<a href="http://gccupc.org/gnu-upc-info/gnu-upc-install-from-source-code">
-configuration page</a>.
-</p>
-
-<p>For a quick summary of the switches used to compile and link a UPC program,
-consult the GUPC
-<a href="http://gccupc.org/gnu-upc-info/gnu-upc-compile-options">
-manual page</a>.
-</p>
<h2 id="gupc_discuss">The GNU UPC Discussion List</h2>
--
2.28.0
reply other threads:[~2020-09-20 14:22 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=20200920142243.A5ABE33E1E@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).