diff options
| author | Iain Sandoe <iain@sandoe.co.uk> | 2021-03-17 12:56:49 +0000 |
|---|---|---|
| committer | Iain Sandoe <iain@sandoe.co.uk> | 2021-03-17 19:12:03 +0000 |
| commit | 9c4d77fc1cc363342b5963b07e837d2b017cac43 (patch) | |
| tree | 46b4d1bf81e83170c9df11cfe79d03687ead475c /gcc/ada/gcc-interface/utils.c | |
| parent | f7581eb38eeaa8af64f3cdfe2faf764f5883f16f (diff) | |
| download | gcc-9c4d77fc1cc363342b5963b07e837d2b017cac43.zip gcc-9c4d77fc1cc363342b5963b07e837d2b017cac43.tar.gz gcc-9c4d77fc1cc363342b5963b07e837d2b017cac43.tar.bz2 | |
testsuite, Darwin : Fix match output for asan/memcmp-1.c.
The Darwin part of libasan produces different output for memcmp
cases from other ports. The GCC implementation does produce the
same output for this test as the clang one (modulo the two points
below).
1. To be more compatible with Linux, Darwin testcases that include
string.h should set _FORTIFY_SOURCE=0 since, otherwise, it will be
defaulted on and the _chk versions of the string builtins will be
used.
2. The system tool that handles symbolization (atos) is not reliable
with GCC's DWARF-2 output but, fortunately, all the platform
versions that support the current sanitizers are able to handle
dwarf-3 for this testcase.
gcc/testsuite/ChangeLog:
* c-c++-common/asan/memcmp-1.c: Add _FORTIFY_SOURCE=0 and
-gdwarf-3 to the command line options. Provide Darwin-
specific match lines for the expected output.
Diffstat (limited to 'gcc/ada/gcc-interface/utils.c')
0 files changed, 0 insertions, 0 deletions