Changeset 6bcd464 for general/prog
- Timestamp:
- 01/23/2019 11:05:19 AM (6 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 8.4, 9.0, 9.1, bdubbs/svn, gimp3, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- d0331db
- Parents:
- 31ee0ed
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
r31ee0ed r6bcd464 202 202 </para> 203 203 204 < caution>204 <note> 205 205 <para> 206 On AMD Ryzen processors (family 17h), the non-optimized version of libstd 207 which is compiled at the start of the tests contains one or more opcodes 208 which are not implemented on this CPU family. These will be logged in the 206 The testsuite will generate some messages in the 209 207 <phrase revision="sysv">system log</phrase> 210 208 <phrase revision="systemd">systemd journal</phrase> 211 and will be followed a few minutes later by segmentation faults. Despite212 that, the tests continue to run, apparently normally. But the system may213 reboot before the tests have completed. The normal optimized libraries214 run without thisproblem.209 for traps on invalid opcodes, and for segmentation faults. 210 In themselves these are nothing to worry about, although if the 211 output from the testsuite reports tests which FAIL with such faults 212 then there may be a problem. 215 213 </para> 216 <para> 217 A mitigation is to install gdb 218 <!-- systemd apparently handles this with systemd-coredump --> 219 <phrase revision="sysv">and to run the tests with 'ulimit -C disabled'</phrase> 220 but this does not always prevent the system rebooting. 221 </para> 222 </caution> 214 </note> 223 215 224 216 <para>
Note:
See TracChangeset
for help on using the changeset viewer.