> Is this still necessary after HJ's patch?
Frankly I don't have access to non-sanitizer-enabled platform but if I
manually disable it in libsanitizer/configure, I start getting Asan test
errors which are similiar to e.g.
http://gcc.gnu.org/ml/gcc-testresults/2013-12/msg00189.html
(i386-unknown-freebsd10.0 from Dec 2). I hope Andreas can confirm
whether we still need this patch.
-Y
-----------------------------------------------
From: Jeff Law <l...@redhat.com>
Sent: Tuesday, December 03, 2013 9:01AM
To: Yury Gribov <y.gri...@samsung.com>, Andreas Schwab
<sch...@linux-m68k.org>
Cc: Jakub Jelinek <ja...@redhat.com>, gcc-patches@gcc.gnu.org,
eugeni.stepa...@gmail.com, VandeVondele Joost
<joost.vandevond...@mat.ethz.ch>, Evgeny Gavrin <e.gav...@samsung.com>,
Viacheslav Garbuzov <v.garbu...@samsung.com>
Subject: Re: [PING^2] [PATCH] PR59063
On 12/03/2013 09:01 AM, Jeff Law wrote:
On 12/01/13 23:12, Yury Gribov wrote:
> This is causing all the tests being run on all targets,
> even if libsanitizer is not supported,
> most of them failing due to link errors.
Thanks for the info and sorry about this. I should probably check
non-sanitized platforms as well before commiting patches. Does the
attached patch make sense to you? Worked for me on x64 and x64 with
manually disabled libsanitizer.
[ ... ]
Is this still necessary after HJ's patch?
jeff
