Re: [RFC][PATCH 4/X][libsanitizer] Pass size and pointer info to error reporting functions

2019-09-09 Thread Martin Liška
On 9/6/19 4:46 PM, Matthew Malcomson wrote: > This is taken from upstream LLVM (change made in LLVM svn commit > 351730), but is not a direct cherry-pick of a commit since the commit > does not apply cleanly. As mentioned in the previous email, the cherry-pick will not be needed any longer.

[RFC][PATCH 4/X][libsanitizer] Pass size and pointer info to error reporting functions

2019-09-06 Thread Matthew Malcomson
This makes the error reporting for loadN and storeN much better. In this first draft these are the only functions I will be using and hence this fix is very useful. This is taken from upstream LLVM (change made in LLVM svn commit 351730), but is not a direct cherry-pick of a commit since the

Error reporting functions

2012-10-04 Thread Iyer, Balaji V
Hi Everyone, This question is mainly for some future submission. Am I allowed to use fatal_error (..)? Mainly, I want to use it in cases where I want to say if this error has occurred, I see no reason to go forward with compilation. Thanks, Balaji V. Iyer.

Re: Error reporting functions

2012-10-04 Thread Ian Lance Taylor
On Thu, Oct 4, 2012 at 5:21 PM, Iyer, Balaji V balaji.v.i...@intel.com wrote: This question is mainly for some future submission. Am I allowed to use fatal_error (..)? Mainly, I want to use it in cases where I want to say if this error has occurred, I see no reason to go forward with