search for: evgenii

It's a test for the new interceptor for prlimit. It could be disabled with __GLIBC_PREREQ for 2.13+. On Fri, Aug 19, 2016 at 5:16 PM, Hans Wennborg <hans at chromium.org> wrote: > +Evgenii for msan. > > I suspect the community simply doesn't keep track of what glibc > version is required :-/ > > On Fri, Aug 19, 2016 at 5:10 PM, Brian Cain <brian.cain at gmail.com> wrote: >> When I tested rc1 I found that some of the test suite wouldn't build on >...

Hi Evgenii, I have one question about this (planned) change: what if a function is not inlined? The linker will not ODR merge them with this change, which isn’t great. What makes “internal” linkage more desirable than "linkonce_odr + visibility hidden"? — Mehdi > On Jul 12, 2016, at 6:16 PM...

Hi Evgenii, I was wondering what the status is of your work to attach "internal_linkage" to methods of standard library classes in libc++. The following piece of code doesn't link because a symbol (string::empty) is undefined and it sounds like your work might fix the linkage error I'm seei...

> -----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"...

clang revision is good, but the kernel is probably too new. Evgenii can comment on that. On Sat, Sep 12, 2015 at 3:23 PM, Greg Stark <stark at mit.edu> wrote: > On Sat, Sep 12, 2015 at 11:22 PM, Greg Stark <stark at mit.edu> wrote: > > Checked out a few days ago. It looks like r246697. I suppose I could > > try updating and rebuilding....

...-x86_64-linux-android in the "run lit tests" step on aarch64 android. It looks like you are right about the x86_64-linux bot, we should add check-hwasan there as well. I'll look into it. On Wed, Jan 2, 2019 at 1:39 PM Chandler Carruth <chandlerc at gmail.com> wrote: > > +Evgenii Stepanov > > On Wed, Jan 2, 2019 at 10:42 AM David Greene via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> After updating from trunk today, I am seeing this failure in hwasan: >> >> FAIL: HWAddressSanitizer-x86_64 :: TestCases/sizes.cpp (19011 of 49508) &gt...

Hi, currently LLVM does not handle the conflict between a section and a global _definition_ with the same name well. A section defines a local symbol with the same name (pointing to the start of the section). Depending on the order of declarations, LLVM either silently overrides the section symbol with the global, or crashes with fatal error: error in backend: symbol 'xxx' is already

Evgenii Stepanov <eugeni.stepanov at gmail.com> writes: > See https://reviews.llvm.org/D51364 - a very similar bug was > introduced by a compiler-rt change and then fixed by a revert. Ok, so what do we do about this? D50940 seems to have introduced the problem but it was reverted. The &quot...

...l comfortable about the use of this attribute for namespaces (apart from the reopening issues raised by others), and in particular the application to parts of a class but not the whole class. I just feel that this is leading to semantic trouble. Thanks, MartinO -----Original Message----- From: Evgenii Stepanov [mailto:eugeni.stepanov at gmail.com] Sent: 09 November 2015 18:49 To: Robinson, Paul <Paul_Robinson at playstation.sony.com> Cc: Chris Lattner <clattner at apple.com>; sstewartgallus00 at mylangara.bc.ca; llvm-dev at lists.llvm.org; Martin J. O'Riordan <martin.oriordan...

On Tue, May 23, 2017 at 4:39 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com > wrote: > On Tue, May 16, 2017 at 4:33 PM, Evgenii Stepanov > <eugeni.stepanov at gmail.com> wrote: > > On Mon, May 15, 2017 at 6:44 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> Thanks for sending this...

...ols are defined? On Mon, Mar 21, 2016 at 7:55 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > The correct fix is probably to know that section symbols are local and > just allow them to have any name. > > Cheers, > Rafael > > > On 18 March 2016 at 13:25, Evgenii Stepanov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> currently LLVM does not handle the conflict between a section and a >> global _definition_ with the same name well. A section defines a local >> symbol with the same name (pointing to the...

...00000 /lib/x86_64-linux-gnu/ld-2.19.so 0x7f86a7900000-0x7f86a7901000 0x7fff98977000-0x7fff98998000 [stack] 0x7fff989b2000-0x7fff989b4000 [vvar] 0x7fff989b4000-0x7fff989b6000 [vdso] 0xffffffffff600000-0xffffffffff601000 [vsyscall] ==14645==End of process memory map. On Mon, Sep 14, 2015 at 9:46 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com> wrote: > Yes, the kernel is too new. > This bug has a patch set that's compatible with the new kernel and > does not even require -pie: > https://llvm.org/bugs/show_bug.cgi?id=24155 > It breaks MSan ABI though, so we can not apply it...

On Fri, Oct 7, 2016 at 2:48 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com> wrote: > On Fri, Oct 7, 2016 at 2:28 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > > On Fri, Oct 7, 2016 at 1:55 PM, Evgenii Stepanov < > eugeni.stepanov at gmail.com> > > wrote: > >> > >> On...

On Fri, Mar 18, 2016 at 01:25:17PM -0700, Evgenii Stepanov via llvm-dev wrote: > Another option is to allow the conflict, and make the global always > override the section symbol. This is easy to do in the integrated > assembler, but it appears that GAS simply does not work this way. Don't we have a similar case for STT_FILE already?...

Thanks Florian. Tim you said: > Some cases can be undone by rematerialization, but not all, and it can involve a lot of effort which increases compile time. Do you have examples of cases where rematerialization is not possible? We are interested in learning about any previous attempts at trying to address the issue in RA. Have you tried it? Bardia Mahjour Compiler Optimizations IBM Toronto

On Mon, May 15, 2017 at 6:44 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > Thanks for sending this out. A few comments below. > > On Mon, May 15, 2017 at 5:17 PM, Evgenii Stepanov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> this is a proposal for the implementation of CFI-icall [1] with ThinLTO. >> >> Jumptables are generated in the merged module. To generate a >> jumptable, we need a list of...

...c bug. It seems to be segfaulting in the memset() in allocate_stack.c (from glib) because given stack pointer is null. I'm guessing this is because it read the wrong half of a 64-bit value somewhere but I haven't identified where it goes wrong. ________________________________________ From: Evgenii Stepanov [eugeni.stepanov at gmail.com] Sent: 02 October 2015 22:26 To: Daniel Sanders Cc: David Blaikie; llvm-dev at lists.llvm.org; Konstantin Serebryany Subject: Re: buildbot failure in LLVM on clang-cmake-mips This is quite sad as we can't reliably fix this case with the static asan runtim...

On Fri, Oct 7, 2016 at 1:55 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com> wrote: > On Fri, Oct 7, 2016 at 1:22 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > > On Fri, Oct 7, 2016 at 12:20 PM, Evgenii Stepanov > > <eugeni.stepanov at gmail.com> wrote: > >> > >> I'v...

Hi, There is a problem with the handling of alwaysinline functions in Clang: they are not always inlined. AFAIK, this may only happen when the caller is in the dead code, but then we don't always successfully remove all dead code. Because of this, we may end up emitting an undefined reference for an "inline __attribute__((always_inline))" function. Libc++ relies on the compiler

On Thu, Mar 8, 2018 at 9:11 AM, Will Deacon <will.deacon at arm.com> wrote: > Thanks for the replies. Some comments below. > > On Wed, Mar 07, 2018 at 11:40:41AM -0800, Evgenii Stepanov wrote: >> On Wed, Mar 7, 2018 at 7:48 AM, Dmitry Vyukov <dvyukov at google.com> wrote: >> > On Wed, Mar 7, 2018 at 4:39 PM, Andrey Ryabinin <aryabinin at virtuozzo.com> wrote: >> >> On 03/06/2018 08:58 PM, Will Deacon wrote: >> >>> Hi a...