search for: sourav0311

> On Apr 1, 2020, at 2:56 AM, Sourabh Singh Tomar <sourav0311 at gmail.com> wrote: > > > Do you mean documenting the desired frontend behavior, or adding some verifier in > LLVM? A warning for the latter is that SROA may currently emit IR that contains a > mix of declares and values for different fragments of an aggregate variable, so I &g...

> On Mar 30, 2020, at 11:57 PM, Sourabh Singh Tomar <sourav0311 at gmail.com> wrote: > >> > My understanding is that this isn't correct: dbg.declare specifies the >> memory address of a variable for the whole lifetime of the function, >> whereas dbg.value (and dbg.addr) specify the value/address until the >> next debug intr...

Thanks, David for updating us. Regarding, mail address, can use anyone{@gmail or @amd}. but sourav0311 at gmail.com works best for me for mailing lists related stuff. Regarding, GDB side of DWARFv5 side of things, we've testing GDB-8.3 WRT DWARFv5 clang and gcc binaries to get better idea of debuggability of clang generated binaries with GDB. Primary motivation being GDB better handling of gcc...

Hi Tom, I do not have SVN account, for accessing LLVM. Thanks, Sourabh On Tue 29 Oct, 2019, 9:08 AM Tom Stellard, <tstellar at redhat.com> wrote: > On 10/26/2019 03:39 AM, Sourabh Singh Tomar wrote: > > Hi All, > > > > I recently requested Chris regarding commit access to LLVM. > > He asked me to wait till the GitHub migration completes and then ask in >

...; > This usually indicates a missing dependency in our CMakeLists.txt, if > you restart the build a couple of times it will likely succeed. > > I will try to fix this missing dependency today. > > -- > Mehdi > > > On Tue, Dec 24, 2019 at 1:37 AM Sourabh Singh Tomar <sourav0311 at gmail.com> > wrote: > >> Hello everyone, >> >> Since MLIR landed today. I'm trying to build it using >> cmake ../llvm/ -DCMAKE_BUILD_TYPE=RELEASE -DLLVM_TARGETS_TO_BUILD=X86 >> -DLLVM_ALL_PROJECTS="clang;lld;lldb;mlir" -DBUILD_SHARED_LIBS=ON &...

Hello everyone, Since MLIR landed today. I'm trying to build it using cmake ../llvm/ -DCMAKE_BUILD_TYPE=RELEASE -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_ALL_PROJECTS="clang;lld;lldb;mlir" -DBUILD_SHARED_LIBS=ON -DCLANG_DEFAULT_LINKER:STRING=lld and also by adding -DLLVM_ALL_PROJECTS. It's giving this compilation error -- Building CXX object

...s in-tree development is preferred, this might be the sort of thing worth prototyping out of tree first to see if it can be made viable before adding the complexity to the LLVM project proper - but I'm open to ideas/suggestions. > > On Wed, Apr 15, 2020 at 3:15 AM Sourabh Singh Tomar <sourav0311 at gmail.com <mailto:sourav0311 at gmail.com>> wrote: > Hello Everyone, > > I need to have your thoughts on this. > > Consider the following test case -- > ------------------------------------------- > 1 int main(int Argc, char **Argv) { > 2 int Lo...

Hello Everyone, I need to have your thoughts on this. Consider the following test case -- ------------------------------------------- 1 int main(int Argc, char **Argv) { 2 int Local = 6; 3 printf("%d\n",Local); 4 5 { 6 printf("%d\n",Local); 7 int Local = 7; 8 printf("%d\n",Local); 9 }

...r assign the bug to yourself. > > > > I looked up the two PRs you cited; PR43622 is likely a simple oversight > that should be easy to fix. PR43263 doesn’t appear to be related to debug > info, was that a typo? > > --paulr > > > > *From:* Sourabh Singh Tomar <sourav0311 at gmail.com> > *Sent:* Wednesday, October 09, 2019 2:38 PM > *To:* David Blaikie <dblaikie at gmail.com> > *Cc:* Adrian Prantl <aprantl at apple.com>; Robinson, Paul < > paul.robinson at sony.com>; Eric Christopher <echristo at gmail.com>; Jonas > Devliegh...

Hi llvm-dev, cfe-dev, It's been a while since our team is investigating DebugInfo in LLVM, we're looking forward to contribute and enhance in LLVM DebugInfo. We,'ve been investigating mostly on DWARF-5 aspects -- couple of them to mention-- 1. Language aspects 2. Location mostly optimized out ones 3. DebugInfo conformance to DWARF-5 To avoid getting conflicted with some body

Hello Everyone, I would like to have your thoughts on this. Overview of the problem =================== While implementing support for the DWARFv5 debug_macro section support in LLVM. I came across these holes: - The macros infrastructure in CLANG/LLVM is inherently tied to a particular version(v4 macinfo). For instance, consider this snippet from CLANG:

> On Mar 30, 2020, at 4:13 AM, Jeremy Morse via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Sourabh, > > On Mon, Mar 30, 2020 at 8:09 AM Sourabh Singh Tomar via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Under what circumstances should a frontend choose to emit(at -O0(No optimization)) llvm.dbg.value for a local variable. >> >> I