fix the link appearance in the online reference pages (#987)

* fix the link appearance in the online reference pages

* revert a few unintended extension changes

Author: bashbaug

OpenCL_C.txt

@@ -605,9 +605,9 @@ constructed from the built-in <<built-in-scalar-data-types,scalar>>,
 <<other-built-in-data-types,other>> data types are supported, with specified
 <<restrictions,restrictions>>.
 
-The following tables describe the other built-in data types in OpenCL
-described in <<table-other-builtin-types>> and the corresponding data type
-available to the application:
+The following tables describe the other built-in data types in OpenCL described
+in <<table-other-builtin-types,Other Built-in Data Types>> and the corresponding
+data type available to the application:
 
 [cols=",",]
 |====
@@ -639,8 +639,9 @@ available to the application:
 
 The data type names described in the following table are reserved and cannot
 be used by applications as type names.
-The vector data type names defined in <<table-builtin-vector-types>>, but
-where _n_ is any value other than 2, 3, 4, 8 and 16, are also reserved.
+The vector data type names defined in <<table-builtin-vector-types,Built-in
+Vector Data Types>>, but where _n_ is any value other than 2, 3, 4, 8 and 16,
+are also reserved.
 
 [[table-reserved-types]]
 .Reserved Data Types
@@ -1031,8 +1032,10 @@ The following names are reserved for use as keywords in OpenCL C and shall
 not be used otherwise.
 
   * Names reserved as keywords by C99.
-  * OpenCL C data types defined in <<table-builtin-vector-types>>,
-    <<table-other-builtin-types>>, and <<table-reserved-types>>.
+  * OpenCL C data types defined in <<table-builtin-vector-types,Built-in Vector
+    Data Types>>,
+    <<table-other-builtin-types,Other Built-in Data Types>>, and
+    <<table-reserved-types,Reserved Data Types>>.
   * Address space qualifiers: `{global}`, `global`, `{local}`, `local`,
     `{constant}`, `constant`, `{private}`, and `private`.
     `{generic}` and `generic` are reserved for future use.
@@ -1050,8 +1053,8 @@ not be used otherwise.
 === Implicit Conversions
 
 Implicit conversions between scalar built-in types defined in
-<<table-builtin-scalar-types>> (except `void` and `half`
-footnote:[{fn-cl_khr_fp16}]) are supported.
+<<table-builtin-scalar-types,Built-in Scalar Data Types>> (except `void` and
+`half` footnote:[{fn-cl_khr_fp16}]) are supported.
 When an implicit conversion is done, it is not just a re-interpretation of
 the expression's value but a conversion of that value to an equivalent value
 in the new type.
@@ -1073,8 +1076,8 @@ Implicit conversions for pointer types follow the rules described in the
 === Explicit Casts
 
 Standard typecasts for built-in scalar data types defined in
-<<table-builtin-scalar-types>> will perform appropriate conversion (except
-`void` and `half` footnote:[{fn-cl_khr_fp16}]).
+<<table-builtin-scalar-types,Built-in Scalar Data Types>> will perform
+appropriate conversion (except `void` and `half` footnote:[{fn-cl_khr_fp16}]).
 In the example below:
 
 [source,opencl_c]
@@ -1374,12 +1377,12 @@ u.d = 1.0;  // u.u contains 0x3ff00000 (big endian) or 0
 
 [open,refpage='as_typen',desc='Reinterpreting Types',type='freeform',spec='clang',anchor='reinterpreting-types-using-as_type-and-as_typen',xrefs='convert_T scalarDataTypes vectorDataTypes']
 --
-All data types described in <<table-builtin-scalar-types>> and
-<<table-builtin-vector-types>> (except `bool`, `void`, and `half`
-footnote:[{fn-cl_khr_fp16}]) may be also reinterpreted as another data type of
-the same size using the *as_type*() operator for scalar data types and the
-*as_type__n__*() operator footnote:[{fn-reinterpret-vector-types}] for vector
-data types.
+All data types described in <<table-builtin-scalar-types,Built-in Scalar Data
+Types>> and <<table-builtin-vector-types,Built-in Vector Data Types>> (except
+`bool`, `void`, and `half` footnote:[{fn-cl_khr_fp16}]) may be also
+reinterpreted as another data type of the same size using the *as_type*()
+operator for scalar data types and the *as_type__n__*() operator
+footnote:[{fn-reinterpret-vector-types}] for vector data types.
 When the operand and result type contain the same number of elements, the
 bits in the operand shall be returned directly without modification as the
 new type.
@@ -1804,7 +1807,8 @@ If all three expressions are scalar values, the C99 rules for ternary
 operator are followed.
 If the result is a vector value, then this is equivalent to calling
 *select*(_exp3_, _exp2_, _exp1_).
-The *select* function is described in <<table-builtin-relational>>.
+The *select* function is described in <<table-builtin-relational,Built-in Scalar
+and Vector Relational Functions>>.
 The second and third expressions can be any type, as long their types match,
 or there is an <<implicit-conversions,implicit conversion>> that can be
 applied to one of the expressions to make their types match, or one is a
@@ -1950,10 +1954,10 @@ operator (*=*), like
 * _lvalue_ = _expression_
 
 The assignment operator stores the value of _expression_ into _lvalue_.
-The _expression_ and _lvalue_ must have the same type, or the expression
-must have a type in <<table-builtin-scalar-types>>, in which case an
-implicit conversion will be done on the expression before the assignment is
-done.
+The _expression_ and _lvalue_ must have the same type, or the expression must
+have a type in <<table-builtin-scalar-types,Built-in Scalar Data Types>>, in
+which case an implicit conversion will be done on the expression before the
+assignment is done.
 
 If _expression_ is a scalar type and _lvalue_ is a vector type, the scalar
 is converted to the element type used by the vector operand.
@@ -2827,12 +2831,12 @@ to OpenCL C with the generic address space.
 *Clause 6.2.5 - Types*:
 
 If address space qualifier on type T is omitted refer to
-<<addr-spaces-inference>>.
+<<addr-spaces-inference,Address Space Inference>>.
 
 *Clause 6.3.2.3 - Pointers*
 
-Conversions between disjoint address spaces are disallowed in OpenCL
-(<<addr-spaces-conversions>>).
+Conversions between disjoint address spaces are disallowed in OpenCL,
+refer to <<addr-spaces-conversions,Address Space Conversions>>.
 
 *Clause 6.5.8 - Relational operators*:
 
@@ -3127,7 +3131,7 @@ representation of the computational _width_ of the `{kernel}`, and should
 serve as the basis for calculating processor bandwidth utilization when the
 compiler is looking to autovectorize the code.
 In the `+__attribute__((vec_type_hint(<type>)))+` qualifier <type> is one of
-the built-in vector types listed in <<table-builtin-vector-types>> or the
+the built-in vector types listed in <<table-builtin-vector-types,Built-in Vector Data Types>> or the
 constituent scalar element types.
 If `vec_type_hint (<type>)` is not specified, the kernel is assumed to have
 the `+__attribute__((vec_type_hint(int)))+` qualifier.
@@ -3385,9 +3389,9 @@ do_proc (__global char *pA, short b,
   . A function in an OpenCL program cannot be called `main`.
   . Implicit function declaration is not supported.
   . Program scope variables can be defined with any valid OpenCL C data type
-    except for those in <<table-other-builtin-types>>. Such program scope
-    variables may be of any user-defined type, or a pointer to a user-defined
-    type.
+    except for those in <<table-other-builtin-types,Other Built-in Data Types>>.
+    Such program scope variables may be of any user-defined type, or a pointer
+    to a user-defined type.
 +
 In the presence of shared virtual memory, these pointers or pointer
 members should work as expected as long as they are shared virtual memory
@@ -4578,8 +4582,9 @@ The built-in math functions are not affected by the prevailing rounding mode
 in the calling environment, and always return the same value as they would
 if called with the round to nearest even rounding mode.
 
-The <<table-builtin-math, following table>> describes the list of built-in
-math functions that can take scalar or vector arguments.
+The <<table-builtin-math,Built-in Scalar and Vector Argument Math Functions>>
+table describes the list of built-in math functions that can take scalar or
+vector arguments.
 We use the generic type name `gentype` to indicate that the function can take
 `float`, `float2`, `float3`, `float4`, `float8`, `float16`, `double`
 footnote:double-supported[{fn-double-supported}], `double2`,
@@ -4925,16 +4930,15 @@ all arguments and the return type, unless otherwise specified.
 
 The following table describes the following functions:
 
-  * A subset of functions from <<table-builtin-math>> that are defined with
-    the half_ prefix .
+  * A subset of functions from <<table-builtin-math,Built-in Scalar and Vector
+    Argument Math Functions>> that are defined with the half_ prefix .
     These functions are implemented with a minimum of 10-bits of accuracy,
     i.e. the maximum error value \<= 8192 ulp.
-  * A subset of functions from <<table-builtin-math>> that are defined with
-    the native_ prefix.
+  * A subset of functions from <<table-builtin-math,Built-in Scalar and Vector
+    Argument Math Functions>> that are defined with the native_ prefix.
     These functions may map to one or more native device instructions and
     will typically have better performance compared to the corresponding
-    functions (without the `+native_+` prefix) described in
-    <<table-builtin-math>>.
+    functions without the `+native_+` prefix).
     The accuracy (and in some cases the input range(s)) of these functions
     is implementation-defined.
   * `+half_+` and `+native_+` functions for following basic operations:
@@ -5629,9 +5633,10 @@ operators (*<*, *\<=*, *>*, *>=*, *!=*, *==*) can be used with scalar and
 vector built-in types and produce a scalar or vector signed integer result
 respectively.
 
-The functions described in the <<table-builtin-relational, following table>> can
-be used with built-in scalar or vector types as arguments and return a scalar or
-vector integer result footnote:[{fn-floating-point-exception-nans}].
+The functions described in the <<table-builtin-relational,Built-in Scalar and
+Vector Relational Functions>> table can be used with built-in scalar or vector
+types as arguments and return a scalar or vector integer result
+footnote:[{fn-floating-point-exception-nans}].
 The argument type `gentype` refers to the following built-in types: `char`,
 `char__n__`, `uchar`, `uchar__n__`, `short`, `short__n__`, `ushort`,
 `ushort__n__`, `int`, `int__n__`, `uint`, `uint__n__`, `long`
@@ -6103,11 +6108,13 @@ The suffix _n_ is also used in the function names (i.e. *vload__n__*,
 
 The results of vector data load and store functions are undefined if the
 address being read from or written to is not correctly aligned as described
-in <<table-vector-loadstore>>.
+in <<table-vector-loadstore,Built-in Vector Data Load and Store Functions>>.
 The pointer argument p can be a pointer to `global`, `local`, or `private`
-memory for store functions described in <<table-vector-loadstore>>.
+memory for store functions described in <<table-vector-loadstore,Built-in Vector
+Data Load and Store Functions>>.
 The pointer argument p can be a pointer to `global`, `local`, `constant`, or
-`private` memory for load functions described in <<table-vector-loadstore>>.
+`private` memory for load functions described in
+<<table-vector-loadstore,Built-in Vector Data Load and Store Functions>>.
 
 [NOTE]
 ====
@@ -9835,9 +9842,9 @@ For query functions this may be `read_only`, `write_only` or `read_write`.
 |====
 
 The values returned by *get_image_channel_data_type* and
-*get_image_channel_order* as specified in <<table-image-query>> with the
-`CLK_` prefixes correspond to the `CL_` prefixes used to describe the
-<<opencl-channel-order,image channel order>> and
+*get_image_channel_order* as specified in <<table-image-query,Built-in Image
+Query Functions>> with the `CLK_` prefixes correspond to the `CL_` prefixes used
+to describe the <<opencl-channel-order,image channel order>> and
 <<opencl-channel-data-type,data type>> in the <<opencl-spec,OpenCL
 Specification>>.
 For example, both `CL_UNORM_INT8` and `CLK_UNORM_INT8` refer to an image
@@ -11611,10 +11618,12 @@ as ULP values if the `-cl-unsafe-math-optimizations` compiler option is
 specified when compiling or building an OpenCL program.
 For derived implementations, the operations used in the derivation may
 themselves be relaxed according to the following table.
-The minimum accuracy of math functions not defined in the following table
-when the `-cl-unsafe-math-optimizations` compiler option is specified is as defined
-in <<table-ulp-float-math>> when operating in the full profile, and as
-defined in <<table-ulp-embedded>> when operating in the embedded profile.
+The minimum accuracy of math functions not defined in the following table when
+the `-cl-unsafe-math-optimizations` compiler option is specified is as defined
+in <<table-ulp-float-math,ULP values for single precision built-in math
+functions>> when operating in the full profile, and as defined in
+<<table-ulp-embedded,ULP values for the embedded profile>> when operating in the
+embedded profile.
 The reference value used to compute the ULP value of an arithmetic operation
 is the infinitely precise result.
 0 ulp is used for math functions that do not require rounding.

api/embedded_profile.asciidoc

@@ -150,7 +150,7 @@ profile are listed in the <<embedded-device-queries-table, OpenCL Embedded
 Device Queries>> table.
 
 [[embedded-device-queries-table]]
-.List of supported param_names by <<clGetDeviceInfo>> for embedded profile
+.List of supported param_names by {clGetDeviceInfo} for embedded profile
 [width="100%",cols="<33%,<17%,<50%",options="header"]
 |====
 | Device Info | Return Type | Description

api/opencl_platform_layer.asciidoc

@@ -75,7 +75,7 @@ The information that can be queried using {clGetPlatformInfo} is specified
 in the <<platform-queries-table, Platform Queries>> table.
 
 [[platform-queries-table]]
-.List of supported param_names by <<clGetPlatformInfo>>
+.List of supported param_names by {clGetPlatformInfo}
 [width="100%",cols="<33%,<17%,<50%",options="header"]
 |====
 | Platform Info | Return Type | Description
@@ -210,7 +210,7 @@ include::{generated}/api/version-notes/clGetDeviceIDs.asciidoc[]
     If _num_devices_ is `NULL`, this argument is ignored.
 
 [[device-types-table]]
-.List of supported device_types by <<clGetDeviceIDs>>
+.List of supported device_types by {clGetDeviceIDs}
 [width="100%",cols="<50%,<50%",options="header"]
 |====
 | Device Type | Description
@@ -331,7 +331,7 @@ device except for the following queries:
   * {CL_DEVICE_REFERENCE_COUNT}
 
 [[device-queries-table]]
-.List of supported param_names by <<clGetDeviceInfo>>
+.List of supported param_names by {clGetDeviceInfo}
 [width="100%",cols="<33%,<17%,<50%",options="header"]
 |====
 | Device Info | Return Type | Description
@@ -1618,7 +1618,7 @@ When a command-queue is created against a sub-device, the commands enqueued
 on the queue are executed only on the sub-device.
 
 [[sub-device-partition-table]]
-.List of supported partition schemes by <<clCreateSubDevices>>
+.List of supported partition schemes by {clCreateSubDevices}
 [width="100%",cols="<33%,<17%,<50%",options="header"]
 |====
 | Partition Property | Partition Value | Description
@@ -1859,7 +1859,7 @@ command-queues, memory, program and kernel objects and for executing kernels
 on one or more devices specified in the context.
 
 [[context-properties-table]]
-.List of supported context creation properties by <<clCreateContext>>
+.List of supported context creation properties by {clCreateContext}
 [width="100%",cols="<33%,<17%,<50%",options="header"]
 |====
 | Context Property | Property Value | Description
@@ -2070,7 +2070,7 @@ _param_value_ by {clGetContextInfo} is described in the
 <<context-info-table, Context Attributes>> table.
 
 [[context-info-table]]
-.List of supported param_names by <<clGetContextInfo>>
+.List of supported param_names by {clGetContextInfo}
 [width="100%",cols="<33%,<17%,<50%",options="header"]
 |====
 | Context Info | Return Type | Description