Hi Andrew!
I tried to run ASan and UBSan tests on installed toolchain, but failed
because current GCC doesn't support this opportunity.
I see, you had fixed this issue
(http://patchwork.ozlabs.org/patch/286866/), but the patch wasn't
applied to GCC. So, I wonder if you are going to commit th
Hi Andrew!
What is the status of this patch? Enabling ASan and UBSan testsuites is
useful for testing installed toolchain, so I wonder if you are going to
commit this.
-Maxim
On Tue, Oct 29, 2013 at 07:56:32AM -0700, Andrew Pinski wrote:
> * lib/ubsan-dg.exp (check_effective_target_fundefined_sanitizer): New
> function.
> (ubsan_init): Save off ALWAYS_CXXFLAGS.
> (ubsan_finish): Restore ALWAYS_CXXFLAGS correctly.
> * lib/asan-dg.exp (check_effective_target_faddress_san
On Tue, Oct 29, 2013 at 7:56 AM, Andrew Pinski
wrote:
> Hi,
> The problem here is that both asan and ubsan testsuite test if we
> have set a library path before running the testsuite. This is
> incorrect when running the already installed testing as there is no
> path to set.
>
> This patch cha
Hi,
The problem here is that both asan and ubsan testsuite test if we
have set a library path before running the testsuite. This is
incorrect when running the already installed testing as there is no
path to set.
This patch changes it so it tests if the executable is able to be
built/linked bef
