search for: min_int

...lt;result> = sdiv nof <ty> <op1>, <op2> ; yields ty:result <result> = udiv nof <ty> <op1>, <op2> ; yields ty:result Overview: If the keyword is present, the compiler can assume no zero values in the denominator. Moreover, for sdiv the division MIN_INT / -1 is prohibited. Otherwise, undefined behavior. Poison value is returned, in case of division by zero or MIN_INT/-1 if the keyword not present. Motivation: In the current state if the loop-vectorizer decides that it should vectorize a loop which contains a predicated integer division -...

...er a different problem related to this late flag setting. The problem is that current SCEV implementation caches a lot of data about SCEVs. In particular, information about ranges and loop backedge taken counts. A side effect of that is that if we had an AddRec like {1,+,1} and cached its range as [MIN_INT, MAX_INT+1), and then later found out that this recurrency provably has <nsw>, its cached range doesn't get updated. As well as ranges of all other SCEVs that depend on that. As result, we have a very weird behavior of SCEV that is unable to prove that sext({1,+,1}<nsw>) is a positi...

...er a different problem related to this late flag setting. The problem is that current SCEV implementation caches a lot of data about SCEVs. In particular, information about ranges and loop backedge taken counts. A side effect of that is that if we had an AddRec like {1,+,1} and cached its range as [MIN_INT, MAX_INT+1), and then later found out that this recurrency provably has <nsw>, its cached range doesn't get updated. As well as ranges of all other SCEVs that depend on that. As result, we have a very weird behavior of SCEV that is unable to prove that sext({1,+,1}<nsw>) is a positi...

...em related to this late flag > setting. The problem is that current SCEV implementation caches a lot of > data about SCEVs. In particular, information about ranges and loop backedge > taken counts. A side effect of that is that if we had an AddRec like {1,+,1} > and cached its range as [MIN_INT, MAX_INT+1), and then later found out that > this recurrency provably has <nsw>, its cached range doesn't get updated. As > well as ranges of all other SCEVs that depend on that. As result, we have a > very weird behavior of SCEV that is unable to prove that sext({1,+,1}<nsw&g...

...elated to this late > flag setting. The problem is that current SCEV implementation caches a > lot of data about SCEVs. In particular, information about ranges and > loop backedge taken counts. A side effect of that is that if we had an > AddRec like {1,+,1} and cached its range as [MIN_INT, MAX_INT+1), and > then later found out that this recurrency provably has <nsw>, its > cached range doesn't get updated. As well as ranges of all other SCEVs > that depend on that. As result, we have a very weird behavior of SCEV > that is unable to prove that sext({1,+,1}...

...th the dynamic libraries (such as pyexpat.pyd - python for win32's convention is .pyd not .so). running the regression testing has been... interesting :) several bugs in wine have been detected, along with faults in the header-files that need to be corrected. tmpfile() is faulty; MAX_LONG and MIN_INT #defines cause problems; the default file format CRLF instead of LF causes the builtin regression test to fail; _ctypes _utterly_ borks on c structure creation and manipulation but is using assembly-stuff (a copy of libffi is included in python) - there are a few more, but out of 350 tests, the maj...

...is late >> flag setting. The problem is that current SCEV implementation caches a >> lot of data about SCEVs. In particular, information about ranges and >> loop backedge taken counts. A side effect of that is that if we had an >> AddRec like {1,+,1} and cached its range as [MIN_INT, MAX_INT+1), and >> then later found out that this recurrency provably has <nsw>, its >> cached range doesn't get updated. As well as ranges of all other SCEVs >> that depend on that. As result, we have a very weird behavior of SCEV >> that is unable to prove that...

Did you ever resolve your problem with Warcraft III? I'm having the same problem. Michael Gerst 21-H-05 One ATT Center Saint Louis, MO 63101 314-235-5443 RESTRICTED-PROPRIETARY INFORMATION The information contained herein is for use only by authorized employees of AT&T Services, Inc., and its authorized affiliates. It is not for general distribution within or outside the respective