Consistently use the --pdb= form in scripts

Stop using the separate argument form (-Wl,-pdb,<filename>), and
prefer using the option form with an implicit output name.
This commit is contained in:
Martin Storsjö committed 2022-10-12 15:28:45 +03:00
1 parent 21d1cf6f18
commit 22b1ff128b
3 files changed
+4 -4

No files matched your search

+2 -2
View File
@@ -231,7 +231,7 @@ for arch in $ARCHS; do
i686|x86_64) ;;
*) continue ;;
esac
$arch-w64-mingw32-clang $test.c -o $TEST_DIR/$test-asan.exe -fsanitize=address -g -gcodeview -Wl,-pdb,$TEST_DIR/$test-asan.pdb
$arch-w64-mingw32-clang $test.c -o $TEST_DIR/$test-asan.exe -fsanitize=address -g -gcodeview -Wl,--pdb=
# Only run these tests on native windows; asan doesn't run in wine.
if [ -n "$NATIVE" ]; then
TESTS_EXTRA="$TESTS_EXTRA $test-asan"
@@ -239,7 +239,7 @@ for arch in $ARCHS; do
fi
if [ -n "$HAS_CFGUARD" ]; then
# Smoke test ASAN with CFGuard to make sure it doesn't trip.
$arch-w64-mingw32-clang $test.c -o $TEST_DIR/$test-asan-cfguard.exe -fsanitize=address -g -gcodeview -Wl,-pdb,$TEST_DIR/$test-asan.pdb -mguard=cf
$arch-w64-mingw32-clang $test.c -o $TEST_DIR/$test-asan-cfguard.exe -fsanitize=address -g -gcodeview -Wl,--pdb= -mguard=cf
if [ -n "$NATIVE" ]; then
TESTS_EXTRA="$TESTS_EXTRA $test-asan-cfguard"
FAILURE_TESTS="$FAILURE_TESTS $test-asan-cfguard"