[www] r341918 - [NFC] Use relative links to llvm.org [No 4]
Johannes Doerfert via llvm-commits
llvm-commits at lists.llvm.org
Tue Sep 11 02:23:27 PDT 2018
Author: jdoerfert
Date: Tue Sep 11 02:23:26 2018
New Revision: 341918
URL: http://llvm.org/viewvc/llvm-project?rev=341918&view=rev
Log:
[NFC] Use relative links to llvm.org [No 4]
Modified:
www/trunk/Features.html
www/trunk/OpenProjects.html
www/trunk/Users.html
www/trunk/header.incl
Modified: www/trunk/Features.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/Features.html?rev=341918&r1=341917&r2=341918&view=diff
==============================================================================
--- www/trunk/Features.html (original)
+++ www/trunk/Features.html Tue Sep 11 02:23:26 2018
@@ -62,7 +62,7 @@ following:</p>
profile-driven, and some simple loop optimizations.</li>
<li>It supports a <a
- href="http://llvm.org/pubs/2004-01-30-CGO-LLVM.html">life-long
+ href="/pubs/2004-01-30-CGO-LLVM.html">life-long
compilation model</a>, including link-time, install-time, run-time, and
offline optimization.</li>
@@ -86,7 +86,7 @@ following:</p>
of development.</li>
<li>LLVM is freely available under an OSI-approved "three-clause BSD" <a
- href="http://llvm.org/docs/FAQ.html#license">license</a>.</li>
+ href="/docs/FAQ.html#license">license</a>.</li>
<li>LLVM is currently used by several commercial entities, who contribute
many extensions and new features.</li>
Modified: www/trunk/OpenProjects.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/OpenProjects.html?rev=341918&r1=341917&r2=341918&view=diff
==============================================================================
--- www/trunk/OpenProjects.html (original)
+++ www/trunk/OpenProjects.html Tue Sep 11 02:23:26 2018
@@ -113,7 +113,7 @@
</ul>
<div class="doc_author">
- <p>Written by the <a href="http://llvm.org/">LLVM Team</a></p>
+ <p>Written by the <a href="/">LLVM Team</a></p>
</div>
<!-- *********************************************************************** -->
@@ -164,7 +164,7 @@ main <a href="https://developers.google.
After instruction selection LLVM uses the MI (Machine Instruction)
representation for programs. We recently added support for reading and
writing this representation to disk
- (<a href="http://llvm.org/docs/MIRLangRef.html">http://llvm.org/docs/MIRLangRef.html</a>). Usage of this format for writing
+ (<a href="/docs/MIRLangRef.html">http://llvm.org/docs/MIRLangRef.html</a>). Usage of this format for writing
tests is growing and so is the desire to improve the format, tools and
workflow. Possible projects:
</p>
@@ -238,7 +238,7 @@ main <a href="https://developers.google.
<!-- *********************************************************************** -->
<div class="www_text">
- <p><b>Description of the project:</b> LLVM functions can be tagged with several <a href="http://llvm.org/docs/LangRef.html#function-attributes">attributes</a> such as the function only reads memory, or the function cannot throw exceptions. These attributes are used by many optimizations when deciding if a particular transformation is valid or not. Functions attributes can be either given by the frontend or be inferred by LLVM.<br>
+ <p><b>Description of the project:</b> LLVM functions can be tagged with several <a href="/docs/LangRef.html#function-attributes">attributes</a> such as the function only reads memory, or the function cannot throw exceptions. These attributes are used by many optimizations when deciding if a particular transformation is valid or not. Functions attributes can be either given by the frontend or be inferred by LLVM.<br>
The goal of this project is to improve current function attributes inference algorithms, and to infer attributes that are not inferred right now. This will be accomplished via intra- and/or inter-procedural analyses. See <a href="http://lists.llvm.org/pipermail/llvm-dev/2018-February/121269.html">this email</a> for a list of oportunities for improvement.</p>
<p><b>Confirmed Mentor:</b> Nuno Lopes</p>
<p><b>Desirable skills:</b> Intermediate knowledge of C++. Optional familiarity with static analysis/abstract interpretation.</p>
@@ -548,7 +548,7 @@ accepted and completed projects, please
<div class="www_text">
<p><b>Description of the project:</b>
ThinLTO is a cool new technology to perform Link-Time Optimization (see
- <a href="http://llvm.org/devmtg/2016-11/#talk12">this talk</a> for more info). It is fairly new
+ <a href="/devmtg/2016-11/#talk12">this talk</a> for more info). It is fairly new
and there are multiple improvements about cross-module optimizations that
can be made there.
</p>
@@ -591,7 +591,7 @@ accepted and completed projects, please
<div class="www_text">
<p><b>Description of the project:</b>
- See <a href="http://llvm.org/devmtg/2016-11/#talk15">this talk</a>
+ See <a href="/devmtg/2016-11/#talk15">this talk</a>
for a starting point. Please take a look at the list of
enhancements and bugs in <a href=
"https://bugs.llvm.org/buglist.cgi?component=opt-viewer&list_id=125824&product=tools&query_format=advanced&resolution=---">
@@ -623,7 +623,7 @@ accepted and completed projects, please
After instruction selection LLVM uses the MI (Machine Instruction)
representation for programs. We recently added support for reading and
writing this representation to disk
- (<a href="http://llvm.org/docs/MIRLangRef.html">http://llvm.org/docs/MIRLangRef.html</a>). Usage of this format for writing
+ (<a href="/docs/MIRLangRef.html">http://llvm.org/docs/MIRLangRef.html</a>). Usage of this format for writing
tests is growing and so is the desire to improve the format, tools and
workflow. Improvements would be welcome:
@@ -820,7 +820,7 @@ accepted and completed projects, please
This check should be easier to write in clang-tidy than in Clang Static
Analyzer, specially because that we don't care about inlining (as long as it
doesn't modify pointer). More details in the
- <a href="https://llvm.org/bugs/show_bug.cgi?id=30232">Bugzilla feature
+ <a href="/bugs/show_bug.cgi?id=30232">Bugzilla feature
request</a>
</p>
<p><b>Confirmed Mentor:</b> Alexander Kornienko, Piotr Padlewski</p>
@@ -989,7 +989,7 @@ accepted and completed projects, please
<p><b>Confirmed Mentor:</b> <a href="mailto:tobias at grosser.es">Tobias Grosser</a></p>
<ul>
- <li>PGO in LLVM: <a href="http://llvm.org/devmtg/2013-11/">2013 developer's meeting presentation</a>
+ <li>PGO in LLVM: <a href="/devmtg/2013-11/">2013 developer's meeting presentation</a>
</ul>
</div>
@@ -1030,7 +1030,7 @@ code generation across functions</p>
<p><b>Confirmed Mentor:</b> <a href="mailto:tobias at grosser.es">Tobias Grosser</a></p>
<ul>
- <li>More about the LLVM Pass manager: <a href="http://llvm.org/devmtg/2014-10/">Chandlers Presentation on 2014 Developer's Meeeting</a>
+ <li>More about the LLVM Pass manager: <a href="/devmtg/2014-10/">Chandlers Presentation on 2014 Developer's Meeeting</a>
</ul>
</div>
@@ -1172,9 +1172,9 @@ of things in the optimizer.
Some specific ones that would be great to have:
<ul>
-<li><a href="http://llvm.org/PR10367">Fix the design of GlobalAlias to not require dest type to match source type</a></li>
-<li><a href="http://llvm.org/PR10368">Redesign ConstantExpr's</a></li>
-<li><a href="http://llvm.org/PR11944">Static constructors should be purged from LLVM</a></li>
+<li><a href="/PR10367">Fix the design of GlobalAlias to not require dest type to match source type</a></li>
+<li><a href="/PR10368">Redesign ConstantExpr's</a></li>
+<li><a href="/PR11944">Static constructors should be purged from LLVM</a></li>
</ul>
</p>
@@ -1243,7 +1243,7 @@ all the back-ends: CBE, llc, and lli.</p
<div class="www_text">
<p>Find benchmarks either using our <a
-href="http://llvm.org/nightlytest/">test results</a> or on your own,
+href="/nightlytest/">test results</a> or on your own,
where LLVM code generators do not produce optimal code or where another
compiler produces better code. Try to minimize the test case that demonstrates
the issue. Then, either <a href="http://bugs.llvm.org/">submit a
@@ -1373,7 +1373,7 @@ improvements to LLVM core</a> are awaiti
<ol>
<li><a href="http://nondot.org/sabre/LLVMNotes/DebugInfoImprovements.txt">Improvements
for Debug Information Generation</a></li>
-<li><a href="http://llvm.org/PR1269">EH support for non-call exceptions</a></li>
+<li><a href="/PR1269">EH support for non-call exceptions</a></li>
<li>Many ideas for feature requests are stored in LLVM bugzilla. Search<a
href="http://bugs.llvm.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=new-feature&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=All+PRs&newqueryname=&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=">for bugs with a "new-feature" keyword</a>.</li>
</ol>
@@ -1400,7 +1400,7 @@ themselves. We want to take advantage o
<li>The alias analysis API supports the getModRefBehavior method, which allows
the implementation to give details analysis of the functions. For example, we
- could implement <a href="http://llvm.org/PR1604">full knowledge of
+ could implement <a href="/PR1604">full knowledge of
printf/scanf</a> side effects, which would be useful. This feature is in
place but not being used for anything right now.</li>
@@ -1431,7 +1431,7 @@ it seems. Maybe the solution is to have
something and change sys headers to use it.</p>
<li>There are lots of ways to optimize out and <a
-href="http://llvm.org/PR452">improve handling of
+href="/PR452">improve handling of
memcpy/memset</a>.</li>
</ol>
@@ -1516,7 +1516,7 @@ link-time optimizations for code size op
</li>
<li>Type inference (aka. devirtualization)</li>
<li><a href="http://nondot.org/sabre/LLVMNotes/BuiltinUnreachable.txt">Value
- assertions</a> (also <a href="http://llvm.org/PR810">PR810</a>).</li>
+ assertions</a> (also <a href="/PR810">PR810</a>).</li>
</ol>
</div>
Modified: www/trunk/Users.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/Users.html?rev=341918&r1=341917&r2=341918&view=diff
==============================================================================
--- www/trunk/Users.html (original)
+++ www/trunk/Users.html Tue Sep 11 02:23:26 2018
@@ -13,7 +13,7 @@ note telling us about your use so that w
</p><p>
This page has only brief entries. Some of these projects are
described in more detail on the
-<a href="http://llvm.org/ProjectsWithLLVM/"> "Projects Using LLVM"</a> page.
+<a href="/ProjectsWithLLVM/"> "Projects Using LLVM"</a> page.
</p>
<div class="www_subsection">LLVM Distributions</div>
@@ -39,7 +39,7 @@ described in more detail on the
<tr>
<td>Adobe Systems Incorporated</td>
<td>Optimizer and JIT codegen for the <a
- href="http://llvm.org/ProjectsWithLLVM/#adobe-hydra">Hydra Language</a>.</td>
+ href="/ProjectsWithLLVM/#adobe-hydra">Hydra Language</a>.</td>
</tr>
<!-- From Adobe web site -->
@@ -47,7 +47,7 @@ described in more detail on the
<td>Adobe Systems Incorporated</td>
<td><a href="http://labs.adobe.com/wiki/index.php/Alchemy">Alchemy C/C++ Compiler for the ActionScript
Virtual Machine (AVM2)</a>. See the <A href="http://labs.adobe.com/wiki/index.php/Alchemy:FAQ">FAQ</a>
- and <a href="http://llvm.org/devmtg/2008-08/">Scott Petersen's DevMtg talk</a> for more details.</td>
+ and <a href="/devmtg/2008-08/">Scott Petersen's DevMtg talk</a> for more details.</td>
</tr>
<!-- CS Department Web Page and Adobe web site -->
@@ -148,7 +148,7 @@ described in more detail on the
<tr>
<td>Intel</td>
<td>
- <a href="http://llvm.org/devmtg/2011-11/Rotem_IntelOpenCLSDKVectorizer.pdf">
+ <a href="/devmtg/2011-11/Rotem_IntelOpenCLSDKVectorizer.pdf">
OpenCL</a></td>
</tr>
@@ -273,7 +273,7 @@ multi-core code generation to the compil
<!-- Authorized and described by Gary Benson, Lead on the Shark JIT
within IcedTea -->
<tr>
- <td><a href="http://llvm.org/ProjectsWithLLVM/#IcedTea">
+ <td><a href="/ProjectsWithLLVM/#IcedTea">
IcedTea Version of Sun's OpenJDK</a></td>
<td>Uses LLVM as JIT on architectures other than x86 and Sparc.</td>
</tr>
Modified: www/trunk/header.incl
URL: http://llvm.org/viewvc/llvm-project/www/trunk/header.incl?rev=341918&r1=341917&r2=341918&view=diff
==============================================================================
--- www/trunk/header.incl (original)
+++ www/trunk/header.incl Tue Sep 11 02:23:26 2018
@@ -93,8 +93,8 @@
<a href="http://lab.llvm.org:8011/">Buildbot</a>
<a href="http://green.lab.llvm.org/green/">Green Dragon</a>
<a href="http://lnt.llvm.org/">LNT</a>
- <a href="http://llvm.org/reports/coverage/">Coverage</a>
- <a href="http://llvm.org/reports/scan-build/">Scan-build</a>
+ <a href="/reports/coverage/">Coverage</a>
+ <a href="/reports/scan-build/">Scan-build</a>
<a href="http://lab.llvm.org:8080/coverage/coverage-reports/index.html">llvm-cov</a>
</div>
More information about the llvm-commits
mailing list