Displaying 5 results from an estimated 5 matches for "dbgerr".
Did you mean:
dbg_err
2010 Jun 14
0
[LLVMdev] Win32 COFF Support
...or k = (*i)->Relocations.begin();
+ k != (*i)->Relocations.end();
+ k++) {
No need to reevaluate ".end()" every iteration of the loop.
+#define dbgout(x) DEBUG(dbgs() << x)
+#define dbgerr(x) do { dbgout (__FILE__ << "(" << __LINE__ <<\
+ ") : " << x << '\n'); llvm_unreachable("unexpected error occured");\
+ } while (false)
+
+#define dbgout_call(x) DEBUG_WITH_TYPE(DEBUG_TYPE"_calls", dbgs() << \...
2010 Jun 12
3
[LLVMdev] Win32 COFF Support
Here is a full patch including Nathan's COFF support, tests that pass
on Windows, and some changes to lit.
Obviously the COFF support and changes to lit should be separate
patches in the end.
http://codereview.appspot.com/1624043/show
- Michael Spencer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: COFF-support.patch
Type: application/octet-stream
Size:
2010 Jun 14
2
[LLVMdev] Win32 COFF Support
...k != (*i)-
> >Relocations.end();
> + k++) {
>
> No need to reevaluate ".end()" every iteration of the loop.
>
>
> +#define dbgout(x) DEBUG(dbgs() << x)
> +#define dbgerr(x) do { dbgout (__FILE__ << "(" << __LINE__ <<\
> + ") : " << x << '\n'); llvm_unreachable("unexpected error
> occured");\
> + } while (false)
> +
> +#define dbgout_call(x) DEBUG_WITH_TYPE(DEBUG_TYPE"_call...
2010 Jun 14
0
[LLVMdev] Win32 COFF Support
...k !=
>> (*i)->Relocations.end();
>> + k++) {
>>
>> No need to reevaluate ".end()" every iteration of the loop.
>>
>>
>> +#define dbgout(x) DEBUG(dbgs() << x)
>> +#define dbgerr(x) do { dbgout (__FILE__ << "(" << __LINE__ <<\
>> + ") : " << x << '\n'); llvm_unreachable("unexpected error occured");\
>> + } while (false)
>> +
>> +#define dbgout_call(x) DEBUG_WITH_TYPE(DEBUG_TYPE&q...
2010 Jun 14
1
[LLVMdev] Win32 COFF Support
On Jun 14, 2010, at 12:41 PM, Nathan Jeffords wrote:
> Michael,
>
> I have not made any changes since I last posted a patch. If you would like to make the final updates, thats fine by me. I don't mind making the changes either, I can have them done this evening as well.
>
> Chris,
>
> As far as naming goes, PE/COFF used in Microsoft's document because they are