Changes in chapter08/gcc.xml [30f3041:60f6d26]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/gcc.xml
r30f3041 r60f6d26 55 55 <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen> 56 56 --> 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> 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> 66 62 67 63 <para>The GCC documentation recommends building GCC in a dedicated build directory:</para> … … 161 157 <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> 162 158 163 <para>Eleven tests in the i386 test suite for the gcc compiler are known to FAIL. 164 It's because the test files do not account for the 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 165 171 <parameter>--enable-default-pie</parameter> option.</para> 166 172 167 <para>Four tests related to PR100400 may be reported 168 as both XPASS and FAIL when testing the g++ compiler; the test file 173 <para>In gcc tests, the tests related to 174 <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>, and 180 many <filename>sve/pcs</filename> tests are known 181 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 for 183 the <parameter>--enable-default-ssp</parameter> option.</para> 184 185 <para>In g++, four tests related to PR100400 are known to be reported 186 as both XPASS and FAIL. It's because the test file for this known issue 169 187 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>, 197 one gcc tests related to <filename>auto-init-7.c</filename>, and 198 four gcc tests related to <filename>vqdmlalh_laneq*.c</filename> 199 are known to fail.</para> 200 201 <!-- Need further investigation --> 202 <para>Many gcc and g++ tests related to hwasan are known to fail.</para> 170 203 171 204 <para>A few unexpected failures cannot always be avoided. The GCC developers … … 224 257 platform-specific differences in the dynamic linker name):</para> 225 258 226 <screen><computeroutput>[Requesting program interpreter: /lib 64/ld-linux-x86-64.so.2]</computeroutput></screen>259 <screen><computeroutput>[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]</computeroutput></screen> 227 260 228 261 <para>Now make sure that we're set up to use the correct start files:</para> … … 232 265 <para>The output of the last command should be:</para> 233 266 234 <screen><computeroutput>/usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded235 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded236 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>267 <screen><computeroutput>/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded 268 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded 269 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen> 237 270 238 271 <para>Depending on your machine architecture, the above may differ slightly. … … 251 284 252 285 <screen><computeroutput>#include <...> search starts here: 253 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/include286 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include 254 287 /usr/local/include 255 /usr/lib/gcc/ x86_64-pc-linux-gnu/&gcc-version;/include-fixed288 /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include-fixed 256 289 /usr/include</computeroutput></screen> 257 290 … … 266 299 be ignored, but otherwise the output of the last command should be:</para> 267 300 268 <screen><computeroutput>SEARCH_DIR("/usr/ x86_64-pc-linux-gnu/lib64")301 <screen><computeroutput>SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib64") 269 302 SEARCH_DIR("/usr/local/lib64") 270 303 SEARCH_DIR("/lib64") 271 304 SEARCH_DIR("/usr/lib64") 272 SEARCH_DIR("/usr/ x86_64-pc-linux-gnu/lib")305 SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib") 273 306 SEARCH_DIR("/usr/local/lib") 274 307 SEARCH_DIR("/lib") 275 308 SEARCH_DIR("/usr/lib");</computeroutput></screen> 276 309 <!-- 277 310 <para>A 32-bit system may use a few other directories. For example, here 278 311 is the output from an i686 machine:</para> … … 286 319 SEARCH_DIR("/lib") 287 320 SEARCH_DIR("/usr/lib");</computeroutput></screen> 288 321 --> 289 322 <para>Next make sure that we're using the correct libc:</para> 290 323 … … 302 335 platform-specific differences in dynamic linker name):</para> 303 336 304 <screen><computeroutput>found ld-linux- x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>337 <screen><computeroutput>found ld-linux-aarch64.so.1 at /usr/lib/ld-linux-aarch64.so.1</computeroutput></screen> 305 338 306 339 <para>If the output does not appear as shown above or is not received
Note:
See TracChangeset
for help on using the changeset viewer.