Displaying 4 results from an estimated 4 matches for "llvm_disable_crash_report".
2015 Jan 27
4
[LLVMdev] [Windows] Cleaning up dialog box suppression code.
We have multiple different places where we handle dialog box
suppression to various degrees. I recently discovered another place we
need to do it, and so I wanted to unify all of them.
We currently have most of this suppression logic behind the
LLVM_DISABLE_CRASH_REPORT environment variable. I would like to make
it unconditional. I don't believe we have any users that desire the
dialog box behavior, as all of our tools are used via the command line
and can report crashes via stderr.
I wanted to check with other Windows users/vendors for exactly which
behavior...
2017 May 23
2
bugpoint, LLVM tools (opt, llc, etc), and symbolizing costs
test/BugPoint/metadata.ll
Takes about 6 seconds to run if llvm-symbolizer isn't present
13 seconds with debug info
1m30s with split DWARF/Fission
So, couple of things:
1) llvm-symbolizer is /really slow/ on split-dwarf files...
2) Why are stack traces even attempted when using bugpoint? Even if it's
just the 6->13s slowdown, that's still halving the speed of bugpoint in the
2017 May 24
1
bugpoint, LLVM tools (opt, llc, etc), and symbolizing costs
On Tue, May 23, 2017 at 2:40 PM Reid Kleckner <rnk at google.com> wrote:
> We have the LLVM_DISABLE_CRASH_REPORT environment variable, but that's
> more about whether we should do crash reporting or not.
>
> It would be pretty reasonable to have another one to disable all this
> stuff. It would also be reasonable to have a cmake option that compiles
> this stuff away, since it basically nev...
2013 Nov 11
3
[LLVMdev] [cfe-dev] Goal for 3.5: Library-friendly headers
On 11/11/2013 19:08, Chris Lattner wrote:
> On Nov 11, 2013, at 9:56 AM, Alp Toker <alp at nuanti.com
> <mailto:alp at nuanti.com>> wrote:
>> Done :-)
>>
>> The patchset is 532K so I've put it online:
>>
>> http://www.nuanti.com/tmp/llvm-api-stability/
>>
>> The bulk edits are split out and noted. They were refactored with an