Hi all,

This patch sets up proper library path for SPEC benchmarks (otherwise some tests fail because trunk libstdc++ uses some new symbols) and also allows users to specify monitor_specrun_wrapper option.

Does this look sane? Could someone commit it?

And while at it - is there a chance to switch from using CLANG/CLANGXX to a more traditional CC/CXX?

Best regards,
Yury Gribov

--
You received this message because you are subscribed to the Google Groups 
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.
Index: spec/run_spec_clang_asan.sh
===================================================================
--- spec/run_spec_clang_asan.sh	(revision 2272)
+++ spec/run_spec_clang_asan.sh	(working copy)
@@ -54,6 +54,7 @@
 else
   F_ASAN='-fsanitize=address -static-libasan'
   CLANGXX=${CLANGXX:-$(echo $CLANG | sed -e 's/gcc$/g++/')}
+  export LD_LIBRARY_PATH=$($CLANG -print-search-dirs | sed -ne 's/^libraries: =//p')${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
 fi
 rm -rf config/$name.*
 
@@ -68,6 +69,7 @@
 
 cat << EOF > config/$name.cfg
 monitor_wrapper = $SPEC_WRAPPER  \$command
+monitor_specrun_wrapper = $SPECRUN_WRAPPER  \$command
 ignore_errors = yes
 tune          = base
 ext           = $name

Reply via email to