On Fri, Apr 05, 2013 at 11:46:44AM +0200, Bernhard Reutner-Fischer wrote:
> > >> --- a/libsanitizer/sanitizer_common/sanitizer_allocator.cc
> > >> +++ b/libsanitizer/sanitizer_common/sanitizer_allocator.cc
> > >> @@ -9,11 +9,13 @@
> > >> // run-time libraries.
> > >> // This allocator that is use
On 5 April 2013 08:42, Konstantin Serebryany
wrote:
>
> On Fri, Apr 5, 2013 at 10:37 AM, Jakub Jelinek wrote:
> > On Thu, Apr 04, 2013 at 09:53:30PM +0200, Bernhard Reutner-Fischer wrote:
> >> uClibc can be built without Largefile support, add the corresponding
> >> guards. uClibc does not have _
On Fri, Apr 5, 2013 at 10:37 AM, Jakub Jelinek wrote:
> On Thu, Apr 04, 2013 at 09:53:30PM +0200, Bernhard Reutner-Fischer wrote:
>> uClibc can be built without Largefile support, add the corresponding
>> guards. uClibc does not have __libc_malloc()/__libc_free(), add guard.
>
> Ugh, this is very
On Thu, Apr 04, 2013 at 09:53:30PM +0200, Bernhard Reutner-Fischer wrote:
> uClibc can be built without Largefile support, add the corresponding
> guards. uClibc does not have __libc_malloc()/__libc_free(), add guard.
Ugh, this is very ugly. In addition to the stuff mentioned by Konstantin
that t
[resending in plain text]
On Fri, Apr 5, 2013 at 10:24 AM, Konstantin Serebryany
wrote:
> Hi Bernhard,
>
> The libsanitizer code is the exact copy of some revision of the upstream
> code in LLVM repo.
> libsanitizer/README.gcc:
> Trivial and urgent fixes (portability, build fixes, etc.) may go
uClibc can be built without Largefile support, add the corresponding
guards. uClibc does not have __libc_malloc()/__libc_free(), add guard.
libsanitizer/ChangeLog
2013-03-24 Bernhard Reutner-Fischer
* sanitizer_common/sanitizer_allocator.cc (libc_malloc,
libc_free): Guard with
