search for: flimit

...39;t used anywhere in your app, then it's dead and doesn't seem interesting. > Also consider the case where the caller of foo() (which does explicitly use E) is in a dylib we haven't loaded yet, and thus haven't looked at the debug info for. I want to set that same breakpoint. -flimit-debug-info=0. The entire idea of -gused is that you're building (almost) all of your app with debug info. It's the default because this matches the common scenario. In short, I still don't understand why we'd want to emit all the enumerators just because an enum type is used. :)...

On Nov 9, 2011, at 12:52 PM, Chris Lattner wrote: > > On Nov 9, 2011, at 10:49 AM, Jim Grosbach wrote: >>> >>> It's not good, but people do it. Also constructing enums via & and | etc. It'd be nice to be able to get the name of whatever it is that the code generator actually produced :) >>> >> >> Agreed. LLVM itself does this sort of

...are, what type that I'm not expecting did we get here with?" >> Also consider the case where the caller of foo() (which does explicitly use E) is in a dylib we haven't loaded yet, and thus haven't looked at the debug info for. I want to set that same breakpoint. > > -flimit-debug-info=0. The entire idea of -gused is that you're building (almost) all of your app with debug info. It's the default because this matches the common scenario. > > In short, I still don't understand why we'd want to emit all the enumerators just because an enum type is...

...ly, I'm looking ahead to fiddling things for PS4. We have no use for linkage names in DWARF, for example, so I'd like to turn that off and save some space. We do want .debug_aranges so I'd like to turn that on by default. And there's a little bit of fine-tuning on exactly what -flimit-debug-info applies to, that we'd like to do (that part is obviously on the Clang side rather than the LLVM side). I hope this helps explain what's going on with the "debugger target" and what I want to do with it. (And apologies for not posting this sooner.) --paulr

...-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 particular optimization, but we decided that most of the other optimizations weren’t really helpful, so they were removed. > > which only emits full definitions of classes in the object file that holds and object’s vtable. > > -- adrian >...

...tandalone-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 particular optimization, but we decided that most of the other optimizations weren’t really helpful, so they were removed. Not quite - I refactored the existing optimizations once I figured out what they did & how it generalized, they are still control...

...imit-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 particular optimization, but we decided that most of the other optimizations weren’t really helpful, so they were removed. > > > Not quite - I refactored the existing optimizations once I figured out what they did & how it generalized, they a...

...tandalone-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 particular optimization, but we decided that most of the other optimizations weren’t really helpful, so they were removed. Not quite - I refactored the existing optimizations once I figured out what they did & how it generalized, they are still control...

On Thu, Jun 4, 2015 at 5:33 PM, Reid Kleckner <rnk at google.com> wrote: > On Thu, Jun 4, 2015 at 5:17 PM, Teresa Johnson <tejohnson at google.com> wrote: >> >> Agreed. Although I assume you mean invoke the new pass under a >> ThinLTO-only option so that avail extern are not dropped in the >> compile pass before the LTO link? > > > No, this pass

On Thu, Jun 4, 2015 at 3:58 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > Personally, I think the right approach is to add a bool to > createGlobalDCEPass defaulting to true named something like > IsAfterInlining. In most standard pass pipelines, GlobalDCE runs after > inlining for obvious reasons, so the default makes sense. The special case > is

...r/Options.td (revision 237590) +++ include/clang/Driver/Options.td (working copy) @@ -636,7 +636,7 @@ def flat__namespace : Flag<["-"], "flat_namespace" def flax_vector_conversions : Flag<["-"], "flax-vector-conversions">, Group<f_Group>; def flimited_precision_EQ : Joined<["-"], "flimited-precision=">, Group<f_Group>; def flto_EQ : Joined<["-"], "flto=">, Group<clang_ignored_gcc_optimization_f_Group>; -def flto : Flag<["-"], "flto">, Group<f_Group&gt...

> 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

...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 particular optimization, but we decided that most of the other optimizations weren’t really helpful, so they were removed. > > Not quite - I refactored the existing optimizations once I figured out what they did & how it generalized, they are sti...

quite some speed improvement indeed. attached the updated patch to apply to svn/trunk. j -------------- next part -------------- A non-text attachment was scrubbed... Name: theora-mmx.patch.gz Type: application/x-gzip Size: 8648 bytes Desc: not available Url : http://lists.xiph.org/pipermail/theora-dev/attachments/20040824/5a5f2731/theora-mmx.patch-0001.bin