Changes in chapter08/gcc.xml [54eb9b7:670f55f]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/gcc.xml
r54eb9b7 r670f55f 55 55 <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen> 56 56 --> 57 <para>On ARM64 hosts, set the default directory name for 58 64-bit libraries to <quote>lib</quote>:</para> 59 60 <screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \ 61 -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen> 57 <para>If building on x86_64, change the default directory name for 64-bit 58 libraries to <quote>lib</quote>:</para> 59 60 <screen><userinput remap="pre">case $(uname -m) in 61 x86_64) 62 sed -e '/m64=/s/lib64/lib/' \ 63 -i.orig gcc/config/i386/t-linux64 64 ;; 65 esac</userinput></screen> 62 66 63 67 <para>The GCC documentation recommends building GCC in a dedicated build directory:</para> … … 157 161 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 158 162 159 <para>In gcc tests, the tests related to 160 <filename>fuse_adrp_add_1.c</filename>, 161 <filename>pr63304_1.c</filename>, 162 <filename>pr70120-2.c</filename>, 163 <filename>pr78733.c</filename>, 164 <filename>pr78796.c</filename>, 165 <filename>pr79041-2.c</filename>, 166 <filename>pr94530.c</filename>, 167 <filename>pr94577.c</filename>, 168 <filename>reload-valid-spoff.c</filename>, and 169 many <filename>aapcs64</filename> tests are known to fail. 170 They are because the test files do not account for the 163 <para>In gcc, eleven tests, in the i386 test suite are known to FAIL. 164 It's because the test files do not account for the 171 165 <parameter>--enable-default-pie</parameter> option.</para> 172 173 <para>In gcc tests, the tests related to174 <filename>pr104005.c</filename>,175 <filename>pr103147-10.C</filename>,176 <filename>shrink_wrap_1.c</filename>,177 <filename>stack-check-cfa-1.c</filename>,178 <filename>stack-check-cfa-2.c</filename>,179 <filename>test_frame_17.c</filename>, and180 many <filename>sve/pcs</filename> tests are known181 to fail. The g++ test related to <filename>pr103147-10.C</filename>182 is known to fail. They are because the test files do not account for183 the <parameter>--enable-default-ssp</parameter> option.</para>184 166 185 167 <para>In g++, four tests related to PR100400 are known to be reported 186 168 as both XPASS and FAIL. It's because the test file for this known issue 187 169 is not well written.</para> 188 189 <!-- Already known via gcc-testresults@gcc.gnu.org -->190 <para>On ARM64,191 four g++ tests related to <filename>Waddress-5.C</filename>,192 twelve g++ tests related to <filename>attrs-10.C</filename>,193 four g++ tests related to <filename>declare-simd-8.C</filename>,194 one gcc tests related to <filename>ssa-dom-thread-7.c</filename>,195 one gcc tests related to <filename>fcsel_1.c</filename>,196 one gcc tests related to <filename>mgeneral-regs_3.c</filename>, and197 four gcc tests related to <filename>vqdmlalh_laneq*.c</filename>198 are known to fail.</para>199 200 <!-- Need further investigation -->201 <para>Many gcc and g++ tests related to hwasan are known to fail.202 And, two tests related to <filename>thread_leak1.c</filename> are known203 to fail for both gcc and g++.</para>204 170 205 171 <para>A few unexpected failures cannot always be avoided. The GCC developers … … 258 224 platform-specific differences in the dynamic linker name):</para> 259 225 260 <screen><computeroutput>[Requesting program interpreter: /lib /ld-linux-aarch64.so.1]</computeroutput></screen>226 <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen> 261 227 262 228 <para>Now make sure that we're setup to use the correct start files:</para> … … 266 232 <para>The output of the last command should be:</para> 267 233 268 <screen><computeroutput>/usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded269 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded270 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>234 <screen><computeroutput>/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded 235 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded 236 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen> 271 237 272 238 <para>Depending on your machine architecture, the above may differ slightly. … … 285 251 286 252 <screen><computeroutput>#include <...> search starts here: 287 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/include253 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include 288 254 /usr/local/include 289 /usr/lib/gcc/ aarch64-unknown-linux-gnu/&gcc-version;/include-fixed255 /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed 290 256 /usr/include</computeroutput></screen> 291 257 … … 300 266 be ignored, but otherwise the output of the last command should be:</para> 301 267 302 <screen><computeroutput>SEARCH_DIR("/usr/ aarch64-unknown-linux-gnu/lib64")268 <screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64") 303 269 SEARCH_DIR("/usr/local/lib64") 304 270 SEARCH_DIR("/lib64") 305 271 SEARCH_DIR("/usr/lib64") 306 SEARCH_DIR("/usr/ aarch64-unknown-linux-gnu/lib")272 SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib") 307 273 SEARCH_DIR("/usr/local/lib") 308 274 SEARCH_DIR("/lib") … … 336 302 platform-specific differences in dynamic linker name):</para> 337 303 338 <screen><computeroutput>found ld-linux- aarch64.so.1 at /usr/lib/ld-linux-aarch64.so.1</computeroutput></screen>304 <screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen> 339 305 340 306 <para>If the output does not appear as shown above or is not received
Note:
See TracChangeset
for help on using the changeset viewer.