Displaying 5 results from an estimated 5 matches for "_myfirst".
2008 Dec 31
2
[LLVMdev] Win32 JIT issue + bug in ScheduleDAGSNodes.h?
...HAS_ITERATOR_DEBUGGING
if (size() <= _Pos)
{
_DEBUG_ERROR("vector subscript out of range");
_SCL_SECURE_OUT_OF_RANGE;
}
#endif /* _HAS_ITERATOR_DEBUGGING */
_SCL_SECURE_VALIDATE_RANGE(_Pos < size());
return (*(_Myfirst + _Pos));
}
/Stein Roger
2008 Dec 31
0
[LLVMdev] Win32 JIT issue + bug in ScheduleDAGSNodes.h?
...f (size() <= _Pos)
> {
> _DEBUG_ERROR("vector subscript out of range");
> _SCL_SECURE_OUT_OF_RANGE;
> }
> #endif /* _HAS_ITERATOR_DEBUGGING */
> _SCL_SECURE_VALIDATE_RANGE(_Pos < size());
>
> return (*(_Myfirst + _Pos));
> }
>
>
Okay. I wonder if we can modify it to check that the vector has
elements in it. Could you try this patch and let me know if it works
for you?
-bw
Index: include/llvm/CodeGen/ScheduleDAGSDNodes.h
================================================================...
2008 Dec 31
0
[LLVMdev] Win32 JIT issue + bug in ScheduleDAGSNodes.h?
On Dec 30, 2008, at 4:51 PM, srs wrote:
> 2. There seems to be an issue in ScheduleDAGSDNodes.h when in debug
> mode. The problem is the evaluation of "&SUnits[0];" which ASSERT's in
> VC++'s vector[] implementation (when _HAS_ITERATOR_DEBUGGING is on).
>
> As a work-around, I commented out the debug code (see "patch" below.)
>
> What would the
2009 Jan 01
1
[LLVMdev] Win32 JIT issue + bug in ScheduleDAGSNodes.h?
...{
>> _DEBUG_ERROR("vector subscript out of range");
>> _SCL_SECURE_OUT_OF_RANGE;
>> }
>> #endif /* _HAS_ITERATOR_DEBUGGING */
>> _SCL_SECURE_VALIDATE_RANGE(_Pos < size());
>>
>> return (*(_Myfirst + _Pos));
>> }
>>
>>
>>
> Okay. I wonder if we can modify it to check that the vector has
> elements in it. Could you try this patch and let me know if it works
> for you?
>
> -bw
>
> Index: include/llvm/CodeGen/ScheduleDAGSDNodes.h
>...
2008 Dec 31
4
[LLVMdev] Win32 JIT issue + bug in ScheduleDAGSNodes.h?
Hi all,
While testing my compiler on win32 in JIT mode, I ran into a couple of
issues:
1. I linked the compiler with the lib files resulting from the cmake
created VS.NET build. While everything built just fine, the
ExecutionEngine::create call always returned NULL. The fix was to also
link with JIT.obj (thanks aKor for pointing me in the right direction).
I would have thought that linking