Displaying 20 results from an estimated 528 matches for "serebryani".
Did you mean:
serebryany
2013 Nov 15
2
[LLVMdev] asan coverage
No, not that I am aware of.
On Nov 14, 2013, at 10:15 PM, Kostya Serebryany <kcc at google.com> wrote:
> On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote:
>> The bit code file produced by the stage 1 compiler for one of the files in the clang driver is corrupt and causes the linker for stage 2 to crash.
>
> Is AddressSanitizer involved in
2012 Feb 08
3
[LLVMdev] Static ctors in llvm::Attribute
On Feb 7, 2012, at 4:04 PM, Kostya Serebryany wrote:
> On Tue, Feb 7, 2012 at 3:46 PM, John McCall <rjmccall at apple.com> wrote:
> On Feb 7, 2012, at 2:07 PM, Kostya Serebryany wrote:
> > Slightly formatted/commented patch.
> > WDYT?
>
> This seems to work fine, except that reading a field from a const
> AttrConst is not a constant expression in C++03, so the
2013 Nov 15
2
[LLVMdev] asan coverage
I don’t know yet, but I will let you know as soon as I can.
On Nov 14, 2013, at 10:18 PM, Kostya Serebryany <kcc at google.com> wrote:
> On Fri, Nov 15, 2013 at 10:16 AM, Bob Wilson <bob.wilson at apple.com> wrote:
>> No, not that I am aware of.
>
> So, if my commits did indeed trigger the failures it could be
> something like binary size change that caused
2013 Nov 15
2
[LLVMdev] asan coverage
The bit code file produced by the stage 1 compiler for one of the files in the clang driver is corrupt and causes the linker for stage 2 to crash.
On Nov 14, 2013, at 10:13 PM, Kostya Serebryany <kcc at google.com> wrote:
> What are the symptoms?
>
> On Fri, Nov 15, 2013 at 9:37 AM, Bob Wilson <bob.wilson at apple.com> wrote:
>> I’m waiting to see if this fixes the
2012 Feb 08
0
[LLVMdev] Static ctors in llvm::Attribute
On Tue, Feb 7, 2012 at 4:55 PM, John McCall <rjmccall at apple.com> wrote:
> On Feb 7, 2012, at 4:04 PM, Kostya Serebryany wrote:
>
> On Tue, Feb 7, 2012 at 3:46 PM, John McCall <rjmccall at apple.com> wrote:
>
>> On Feb 7, 2012, at 2:07 PM, Kostya Serebryany wrote:
>> > Slightly formatted/commented patch.
>> > WDYT?
>>
>> This seems to
2013 Nov 15
2
[LLVMdev] asan coverage
Yes. I'm seeing this as well and it predates Kostya's change. Shows up as
memory corruption or double free on Linux.
On Nov 14, 2013 10:46 PM, "Alexey Samsonov" <samsonov at google.com> wrote:
> FYI I've seen what looked like a memory corruption in (private) Clang
> bootstrap process long before Kostya's changes were submitted. I hope I'll
> have the
2013 Nov 15
0
[LLVMdev] asan coverage
On Fri, Nov 15, 2013 at 10:16 AM, Bob Wilson <bob.wilson at apple.com> wrote:
> No, not that I am aware of.
So, if my commits did indeed trigger the failures it could be
something like binary size change that caused different code alignment
or some such
and which triggered a latent memory bug somewhere else.
It's already late evening for you now. Will you have a chance to
reapply
2012 Jun 18
2
[LLVMdev] MemorySanitizer, a tool that finds uninitialized reads and more
On Mon, Jun 18, 2012 at 6:30 PM, Joerg Sonnenberger <joerg at britannica.bec.de
> wrote:
> On Mon, Jun 18, 2012 at 05:52:49PM +0400, Kostya Serebryany wrote:
> > On Mon, Jun 18, 2012 at 5:43 PM, Joerg Sonnenberger <
> joerg at britannica.bec.de
> > > wrote:
> >
> > > On Mon, Jun 18, 2012 at 05:19:11PM +0400, Kostya Serebryany wrote:
> > > >
2013 Nov 15
0
[LLVMdev] asan coverage
FYI I've seen what looked like a memory corruption in (private) Clang
bootstrap process long before Kostya's changes were submitted. I hope I'll
have the chance to investigate it soon.
On Fri, Nov 15, 2013 at 10:20 AM, Bob Wilson <bob.wilson at apple.com> wrote:
> I don’t know yet, but I will let you know as soon as I can.
>
> On Nov 14, 2013, at 10:18 PM, Kostya
2016 Sep 21
2
-sanitizer-coverage-prune-blocks=true and LibFuzzer
> On Sep 21, 2016, at 1:25 PM, Kostya Serebryany <kcc at google.com> wrote:
>
>
>
> On Wed, Sep 21, 2016 at 12:58 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote:
>
>> On Sep 21, 2016, at 12:56 PM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote:
>>
>>
>>
2013 Nov 15
0
[LLVMdev] asan coverage
On Fri, Nov 15, 2013 at 10:14 AM, Bob Wilson <bob.wilson at apple.com> wrote:
> The bit code file produced by the stage 1 compiler for one of the files in the clang driver is corrupt and causes the linker for stage 2 to crash.
Is AddressSanitizer involved in any of the stages of the LTO build?
>
> On Nov 14, 2013, at 10:13 PM, Kostya Serebryany <kcc at google.com> wrote:
2013 Nov 15
2
[LLVMdev] asan coverage
I’m waiting to see if this fixes the buildbots. Unfortunately, because they were failing all day, there are a bunch of other regressions that have come up, and I’m still working through them. It takes quite a while to run a bootstrapped LTO clang build, so it will take a while longer.
I don’t have any other useful information at this point, and I share your puzzlement about how your changes
2013 Nov 15
0
[LLVMdev] asan coverage
I was able to successfully build with r194701, so I have reapplied that along with the compiler-rt changes. Somehow we need to get to the bottom of the problem. If you can reproduce it, please help!!
On Nov 14, 2013, at 11:01 PM, Eric Christopher <echristo at gmail.com> wrote:
> Yes. I'm seeing this as well and it predates Kostya's change. Shows up as memory corruption or
2014 Feb 19
2
[LLVMdev] asan coverage
On Tue, Feb 18, 2014 at 10:15 PM, Bob Wilson <bob.wilson at apple.com> wrote:
> Our instrumentation code is basically done now, so you can try it out and
> compare the performance. Just build with -finstr-profile-generate.
>
Is this in trunk?
clang-3.5: error: unknown argument: '-finstr-profile-generate'
--kcc
> You may want to hack the compiler-rt code in
2012 Jun 18
0
[LLVMdev] MemorySanitizer, a tool that finds uninitialized reads and more
On Mon, Jun 18, 2012 at 06:44:57PM +0400, Kostya Serebryany wrote:
> On Mon, Jun 18, 2012 at 6:30 PM, Joerg Sonnenberger <joerg at britannica.bec.de
> > wrote:
>
> > On Mon, Jun 18, 2012 at 05:52:49PM +0400, Kostya Serebryany wrote:
> > > On Mon, Jun 18, 2012 at 5:43 PM, Joerg Sonnenberger <
> > joerg at britannica.bec.de
> > > > wrote:
> >
2012 Jun 18
2
[LLVMdev] MemorySanitizer, a tool that finds uninitialized reads and more
On Mon, Jun 18, 2012 at 5:43 PM, Joerg Sonnenberger <joerg at britannica.bec.de
> wrote:
> On Mon, Jun 18, 2012 at 05:19:11PM +0400, Kostya Serebryany wrote:
> > On Mon, Jun 18, 2012 at 5:07 PM, Joerg Sonnenberger <
> joerg at britannica.bec.de
> > > wrote:
> >
> > > On Mon, Jun 18, 2012 at 02:39:34PM +0400, Kostya Serebryany wrote:
> > > >
2012 Feb 08
1
[LLVMdev] Static ctors in llvm::Attribute
On Feb 7, 2012, at 4:56 PM, Kostya Serebryany wrote:
>
>
> On Tue, Feb 7, 2012 at 4:55 PM, John McCall <rjmccall at apple.com> wrote:
> On Feb 7, 2012, at 4:04 PM, Kostya Serebryany wrote:
>> On Tue, Feb 7, 2012 at 3:46 PM, John McCall <rjmccall at apple.com> wrote:
>> On Feb 7, 2012, at 2:07 PM, Kostya Serebryany wrote:
>> > Slightly
2014 Jan 09
2
[LLVMdev] [cfe-dev] lsan for LLVM bootstrap; leaks in TableGen
On Dec 25, 2013, at 11:55 PM, Kostya Serebryany <kcc at google.com> wrote:
> On Thu, Dec 26, 2013 at 11:49 AM, Chandler Carruth <chandlerc at google.com> wrote:
>
> On Thu, Dec 26, 2013 at 2:40 AM, Kostya Serebryany <kcc at google.com> wrote:
> Like this?
>
> +extern "C" {
> +// Disable LeakSanitizer, see
2013 Nov 15
0
[LLVMdev] asan coverage
What are the symptoms?
On Fri, Nov 15, 2013 at 9:37 AM, Bob Wilson <bob.wilson at apple.com> wrote:
> I’m waiting to see if this fixes the buildbots. Unfortunately, because they were failing all day, there are a bunch of other regressions that have come up, and I’m still working through them. It takes quite a while to run a bootstrapped LTO clang build, so it will take a while longer.
2016 Dec 08
2
Debug Locations for Optimized Code
> -----Original Message-----
> From: Evgenii Stepanov [mailto:eugeni.stepanov at gmail.com]
> Sent: Wednesday, December 07, 2016 4:51 PM
> To: Kostya Serebryany
> Cc: Robinson, Paul; llvm-dev at lists.llvm.org
> Subject: Re: [llvm-dev] Debug Locations for Optimized Code
>
> In fact, we are already using "parallel" debug info. Frame layout
> descriptions encode