diff options
| author | Tamar Christina <tamar.christina@arm.com> | 2019-10-22 14:25:38 +0000 |
|---|---|---|
| committer | Tamar Christina <tnfchris@gcc.gnu.org> | 2019-10-22 14:25:38 +0000 |
| commit | 761a3a95ee26d54fbb8351c15cf5773d58fc9f70 (patch) | |
| tree | 877fc8c61a6d2d96de5bb0932b80308d35942415 /gcc | |
| parent | 2e30cb8395130982b8b28a4eb42814f4da1fb6d2 (diff) | |
| download | gcc-761a3a95ee26d54fbb8351c15cf5773d58fc9f70.zip gcc-761a3a95ee26d54fbb8351c15cf5773d58fc9f70.tar.gz gcc-761a3a95ee26d54fbb8351c15cf5773d58fc9f70.tar.bz2 | |
Arm: Fix arm libsanitizer bootstrap failure
Glibc has recently introduced changed to the mode field in ipc_perm
in commit 2f959dfe849e0646e27403f2e4091536496ac0f0. For Arm this
means that the mode field no longer has the same size.
This causes an assert failure against libsanitizer's internal copy
of ipc_perm. Since this change can't be easily detected I am adding
arm to the list of targets that are excluded from this check. libsanitizer
doesn't use this field (and others, it in fact uses only 1 field) so this check
can be ignored.
Padding bits were used by glibc when the field was changed so sizeof and offsets
of the remaining fields should be the same.
libsanitizer/ChangeLog:
PR sanitizer/92154
* sanitizer_common/sanitizer_platform_limits_posix.cpp (defined):
Cherry-pick compiler-rt revision r375220.
From-SVN: r277291
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions