aboutsummaryrefslogtreecommitdiff
path: root/archs
diff options
context:
space:
mode:
authorMark Loeser <halcy0n@gentoo.org>2006-05-03 05:24:54 +0000
committerMark Loeser <halcy0n@gentoo.org>2006-05-03 05:24:54 +0000
commit46e0bbce1cab97b532310a22973ee12d08d9fe78 (patch)
tree6a65ebb62c21895bb160380d228b7c1dfa3e4e4c /archs
parentThis should have been an important tag, but wasn't (diff)
downloaddevmanual-46e0bbce1cab97b532310a22973ee12d08d9fe78.tar.gz
devmanual-46e0bbce1cab97b532310a22973ee12d08d9fe78.tar.bz2
devmanual-46e0bbce1cab97b532310a22973ee12d08d9fe78.zip
Adding the last xml files, then I'll fix all of the addresses in one shot
git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/devmanual/trunk@38 176d3534-300d-0410-8db8-84e73ed771c3
Diffstat (limited to 'archs')
-rw-r--r--archs/amd64/text.xml6
-rw-r--r--archs/sparc/text.xml4
2 files changed, 5 insertions, 5 deletions
diff --git a/archs/amd64/text.xml b/archs/amd64/text.xml
index 581fda4..5dbf7b8 100644
--- a/archs/amd64/text.xml
+++ b/archs/amd64/text.xml
@@ -10,7 +10,7 @@
<p>
Gentoo Policy demands all shared objects to be compiled with <c>-fPIC</c>
-in <c>CFLAGS</c>. Since this is only a rule, you *can* break it on some arches.
+in <c>CFLAGS</c>. Since this is only a rule, you <e>can</e> break it on some arches.
You might never notice it. On AMD64, this is a necessity, if shared objects aren't
built with support for position independent code, the build process bails out
with an error message like this:
@@ -37,7 +37,7 @@ pros and cons.
<p>
Sometimes, a simple <c>sed</c> command is enough to fix it, however, the statements
normally aren't very readable and may fail when upstream changes the file.
-Please verify that you only change the <c>CFLAGS</c> for *shared* objects, not for
+Please verify that you only change the <c>CFLAGS</c> for <e>shared</e> objects, not for
the whole package.
</p>
@@ -220,7 +220,7 @@ so-called <c>emul-linux-x86</c> packages, which are located in the
</dt>
<dd>
<p>
- The name says it -- GTK and its engines belong herein.
+ The name says it <d/> GTK and its engines belong herein.
</p>
</dd>
<dt>
diff --git a/archs/sparc/text.xml b/archs/sparc/text.xml
index 669c930..08672e7 100644
--- a/archs/sparc/text.xml
+++ b/archs/sparc/text.xml
@@ -87,7 +87,7 @@ There are three basic SPARC instruction set standards.
</ul>
<p>
-In addition, individual CPU implementations have slight differences -- for
+In addition, individual CPU implementations have slight differences <d/> for
example, HyperSparc CPUs have relaxed requirements when it comes to scheduling
certain instructions. These are relatively minor differences.
</p>
@@ -95,7 +95,7 @@ certain instructions. These are relatively minor differences.
<p>
If <c>gcc</c> is invoked without any <c>-mcpu</c> parameter, it will generate <c>v7</c>
code. Depending upon the application, this can be anywhere up to five times
-slower than <c>v9</c> code when running on an UltraSparc -- cryptographic and
+slower than <c>v9</c> code when running on an UltraSparc <d/> cryptographic and
graphics applications which make heavy use of integer multiplication and
division are especially badly hit. For this reason, the comments in
<uri link="::general-concepts/user-environment#Not Filtering Variables"/>