summaryrefslogtreecommitdiffstats
path: root/llvm/test/CodeGen/AMDGPU/schedule-fs-loop-nested-if.ll
diff options
context:
space:
mode:
authorAdhemerval Zanella <adhemerval.zanella@linaro.org>2016-08-15 21:24:50 +0000
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2016-08-15 21:24:50 +0000
commitced79280697ca4661e36c957f47046cbde124029 (patch)
treecac19c994e7c2d9a995d2b4c63e99fed757eaa65 /llvm/test/CodeGen/AMDGPU/schedule-fs-loop-nested-if.ll
parent28fdc4272d598bdb7b0696ac22c20e9a41836c03 (diff)
downloadbcm5719-llvm-ced79280697ca4661e36c957f47046cbde124029.tar.gz
bcm5719-llvm-ced79280697ca4661e36c957f47046cbde124029.zip
libcxx: Fix path.compare.pass expected result
The expected 'filesystem::path::compare' result states that for different path only result sign contains the information about passed arguments (not its integer value). This is due it uses the output of other compare functions (basic_string_view and char_traits) without further handling and char_traits uses memcmp for final buffer comparison. However for GLIBC on AArch64 the code: int ret = memcmp ("b/a/c", "a/b/c", 1); Results in '64' where for x86_64 it results in '1'. This patch fixes the expected 'filesystem::path::compare' by normalizing all the results before assert comparison. llvm-svn: 278745
Diffstat (limited to 'llvm/test/CodeGen/AMDGPU/schedule-fs-loop-nested-if.ll')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud