search for: fstandalon

Hello, disclaimer/ Apologies if this is the wrong llvm/clang mailing list; please, direct me to the right one if needed. /disclaimer I've been experiencing issues with incomplete type info when debugging code generated by clang 3.5.0 from the recent release_35 branch. Generally, the problem manifests itself as the inability to examine any std::string parameter to a function, in either gdb

...his situation) - so, because the system itself breaks the assumption, the default is to turn off the assumption) I assumed your proposal would only add this debug info to describe the vtable constant where the vtable is defined. Which would break OSX. If the idea would be to, in OSX (& other -fstandalone-debug situations/platforms/users) would be to include this vtable DIE even where the vtable is not defined - that adds a bit more debug info & also it means debug info describing the declaration of a variable, also something we haven't really done in LLVM before - again, technically possib...

If you're going to use clang built binaries with lldb, you'll want to pass -fstandalone-debug - this is the default on platforms where lldb is the primary debugger (Darwin and freebsd) Not sure if that is the problem you are seeing, but will be a problem sooner or later On Mar 26, 2016 4:16 PM, "Jeffrey Tan via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > Hi,...

...#39;m seeing > >> the full description of class B. > > > > by default for darwin, it doesn't do this. For others you must specify -fno-limit-debug-info or some flag like that. > > I think the option is -f(no-)standalone-debug-info > > -fno-limit-debug-info == -fstandalone-debug > (limit-debug-info was the old name & we had a long discussion and decided standalone-debug more aptly described what it should mean/how it should generalize) And if my memory serves correctly, what adds to the confusion is that -flimit-debug-info used to do more than just this part...

...the system itself > breaks the assumption, the default is to turn off the assumption) > > I assumed your proposal would only add this debug info to describe the > vtable constant where the vtable is defined. Which would break OSX. > > If the idea would be to, in OSX (& other -fstandalone-debug > situations/platforms/users) would be to include this vtable DIE even where > the vtable is not defined - that adds a bit more debug info & also it means > debug info describing the declaration of a variable, also something we > haven't really done in LLVM before - again...

...gt; breaks the assumption, the default is to turn off the assumption) >> >> I assumed your proposal would only add this debug info to describe the >> vtable constant where the vtable is defined. Which would break OSX. >> >> If the idea would be to, in OSX (& other -fstandalone-debug >> situations/platforms/users) would be to include this vtable DIE even where >> the vtable is not defined - that adds a bit more debug info & also it means >> debug info describing the declaration of a variable, also something we >> haven't really done in LLV...

...f thing today? In a naïve test, I'm seeing >> the full description of class B. > > by default for darwin, it doesn't do this. For others you must specify -fno-limit-debug-info or some flag like that. I think the option is -f(no-)standalone-debug-info -fno-limit-debug-info == -fstandalone-debug (limit-debug-info was the old name & we had a long discussion and decided standalone-debug more aptly described what it should mean/how it should generalize) And if my memory serves correctly, what adds to the confusion is that -flimit-debug-info used to do more than just this particula...

...30H\213E\350H\211\307\350O\264\312\377H\211ƿ\b", size_ = 0, capacity_ = 1441151880758558720}}}} Jeffrey On Sat, Mar 26, 2016 at 8:22 PM, David Blaikie <dblaikie at gmail.com> wrote: > If you're going to use clang built binaries with lldb, you'll want to pass > -fstandalone-debug - this is the default on platforms where lldb is the > primary debugger (Darwin and freebsd) > > Not sure if that is the problem you are seeing, but will be a problem > sooner or later > On Mar 26, 2016 4:16 PM, "Jeffrey Tan via llvm-dev" < > llvm-dev at lists....

...ption, the default is to turn off the assumption) >>> >>> I assumed your proposal would only add this debug info to describe the >>> vtable constant where the vtable is defined. Which would break OSX. >>> >>> If the idea would be to, in OSX (& other -fstandalone-debug >>> situations/platforms/users) would be to include this vtable DIE even where >>> the vtable is not defined - that adds a bit more debug info & also it means >>> debug info describing the declaration of a variable, also something we >>> haven't re...

On Mon, Mar 5, 2018 at 8:37 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Sat, Mar 3, 2018 at 8:20 PM Daniel Berlin via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> On Fri, Mar 2, 2018 at 3:58 PM, Roman Popov via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> Hi all, >>> >>> As you may know

Hi, While dogfooding our lldb based IDE on Linux, I am seeing a lot of variable evaluation errors related to DW_TAG_member which prevents us from release the IDE. Can anyone help to confirm if they are known issues? If not, any information you need to troubleshoot this issue? Here is one example: (lldb) fr v *error: biggrep_master_server_async 0x10b9a91a: DW_TAG_member '_M_pod_data'

> On May 1, 2015, at 2:18 PM, Greg Clayton <gclayton at apple.com> wrote: > > >> On May 1, 2015, at 2:00 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: >> >>> A few more things that vote for debugger tuning: >>> >>> - LLDB doesn't like to have DWARF that has a class A that inherits from >>> class B, but

...seeing > >> the full description of class B. > > > > by default for darwin, it doesn't do this. For others you must specify -fno-limit-debug-info or some flag like that. > > I think the option is -f(no-)standalone-debug-info > > > -fno-limit-debug-info == -fstandalone-debug > (limit-debug-info was the old name & we had a long discussion and decided standalone-debug more aptly described what it should mean/how it should generalize) > > > > And if my memory serves correctly, what adds to the confusion is that -flimit-debug-info used to do m...

...uot;, > size_ = 0, > capacity_ = 1441151880758558720}}}} > > Jeffrey > > > > On Sat, Mar 26, 2016 at 8:22 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> If you're going to use clang built binaries with lldb, you'll want to >> pass -fstandalone-debug - this is the default on platforms where lldb is >> the primary debugger (Darwin and freebsd) >> >> Not sure if that is the problem you are seeing, but will be a problem >> sooner or later >> On Mar 26, 2016 4:16 PM, "Jeffrey Tan via llvm-dev" < &gt...

On Sat, Mar 3, 2018 at 8:20 PM Daniel Berlin via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Fri, Mar 2, 2018 at 3:58 PM, Roman Popov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi all, >> >> As you may know modern C++ debuggers (GDB and LLDB) support dynamic type >> identification for polymorphic objects, by utilizing C++ RTTI.

...f thing today? In a naïve test, I'm seeing >> the full description of class B. > > by default for darwin, it doesn't do this. For others you must specify -fno-limit-debug-info or some flag like that. I think the option is -f(no-)standalone-debug-info -fno-limit-debug-info == -fstandalone-debug (limit-debug-info was the old name & we had a long discussion and decided standalone-debug more aptly described what it should mean/how it should generalize) And if my memory serves correctly, what adds to the confusion is that -flimit-debug-info used to do more than just this particula...

...s to turn off the assumption) >>>> >>>> I assumed your proposal would only add this debug info to describe the >>>> vtable constant where the vtable is defined. Which would break OSX. >>>> >>>> If the idea would be to, in OSX (& other -fstandalone-debug >>>> situations/platforms/users) would be to include this vtable DIE even where >>>> the vtable is not defined - that adds a bit more debug info & also it means >>>> debug info describing the declaration of a variable, also something we >>>&gt...

...s to turn off the assumption) >>>> >>>> I assumed your proposal would only add this debug info to describe the >>>> vtable constant where the vtable is defined. Which would break OSX. >>>> >>>> If the idea would be to, in OSX (& other -fstandalone-debug >>>> situations/platforms/users) would be to include this vtable DIE even where >>>> the vtable is not defined - that adds a bit more debug info & also it means >>>> debug info describing the declaration of a variable, also something we >>>&gt...

...39;m > >> seeing the full description of class B. > > > > by default for darwin, it doesn't do this. For others you must specify -fno-limit-debug-info or some flag like that. > > I think the option is -f(no-)standalone-debug-info > > -fno-limit-debug-info == -fstandalone-debug (limit-debug-info was the > old name & we had a long discussion and decided standalone-debug more > aptly described what it should mean/how it should generalize) > > And if my memory serves correctly, what adds to the confusion is that -flimit-debug-info used to do more t...

This could be ICF. There were lots of issues with ICF on ARM64, but they are not inherently ARM64-specific, they just come up there more often. See https://reviews.llvm.org/D56986 which fixes that. Easiest thing is always to profile or add /time to see what's slow. On Wed, Feb 27, 2019 at 6:30 AM Leonardo Santagada <santagada at gmail.com> wrote: > Anyone would know why lld takes