On 2 December 2013 20:12, Philip Reames <listmail at philipreames.com> wrote:> Would it make sense to separate our a flag for preserving full and exactly > stack traces? Using -O1 is one option, but it would be nice to move beyond > -O1 with reasonable confidence that stack traces would be preserved. Would > others be interested in such a feature?I can't say I'm interested in that, but it shouldn't be too different than a module-level #pragma optimize (no_this, no_that), which could be supported if the table of flags has a rich enough semantics. cheers, --renato
Renato, I'm not sure I follow. By #pragma, do you mean a C-level thing? By table of flags, some hypothetical place where the proposed "Simple|Speed|Space|Aggressive" setting lives, accessible by IR passes? Sounds like what Philip needs is a more specific PreserveStackTraces setting in the same place, that's on by default at -O1, and overridable by some find of -fpreserve-stack-traces Clang command-line flag. On Tue, Dec 3, 2013 at 2:42 AM, Renato Golin <renato.golin at linaro.org> wrote:> On 2 December 2013 20:12, Philip Reames <listmail at philipreames.com> wrote: >> Would it make sense to separate our a flag for preserving full and exactly >> stack traces? Using -O1 is one option, but it would be nice to move beyond >> -O1 with reasonable confidence that stack traces would be preserved. Would >> others be interested in such a feature? > > I can't say I'm interested in that, but it shouldn't be too different > than a module-level #pragma optimize (no_this, no_that), which could > be supported if the table of flags has a rich enough semantics. > > cheers, > --renato > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On 3 December 2013 09:02, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote:> I'm not sure I follow. By #pragma, do you mean a C-level thing? By > table of flags, some hypothetical place where the proposed > "Simple|Speed|Space|Aggressive" setting lives, accessible by IR > passes?Yes.> Sounds like what Philip needs is a more specific > PreserveStackTraces setting in the same place, that's on by default at > -O1, and overridable by some find of -fpreserve-stack-traces Clang > command-line flag.I see, I seem to have overestimated his needs. ;) cheers, --renato
On 12/3/13 1:02 AM, Evgeniy Stepanov wrote:> Sounds like what Philip needs is a more specific > PreserveStackTraces setting in the same place, that's on by default at > -O1, and overridable by some find of -fpreserve-stack-traces Clang > command-line flag.This was exactly what I was trying to suggest. Thanks for the clarification. Philip