Displaying 5 results from an estimated 5 matches for "scopedrange".
2007 Jul 27
2
[LLVMdev] Couple of changes (2005 and other toolchain related)
...tion support from X86 to PPC).
Thanks,
Jaap Suter - http://jaapsuter.com
* PredicateSimplifier.cpp, line 236, add: friend bool operator<(unsigned to,
const Edge &edge) { return to < edge.To; }
* PredicateSimplifier.cpp, line 677, add: friend bool operator<(const Value
*value, const ScopedRange &range) { return value < range.V; }
Lacking these operators, it generates something like the following:
c:\program files\microsoft visual studio 8\vc\include\xutility(267) : error
C2678: binary '<' : no operator found which takes a left-hand operand of type
'const unsigned...
2007 Jul 27
0
[LLVMdev] Couple of changes (2005 and other toolchain related)
...tion support from X86 to PPC).
Thanks,
Jaap Suter - http://jaapsuter.com
* PredicateSimplifier.cpp, line 236, add: friend bool operator<(unsigned
to,
const Edge &edge) { return to < edge.To; }
* PredicateSimplifier.cpp, line 677, add: friend bool
operator<(const Value
*value, const ScopedRange &range) { return value < range.V; }
Lacking these operators, it generates something like the following:
c:\program files\microsoft visual studio
8\vc\include\xutility(267) : error
C2678: binary '<' : no operator found which takes a left-hand operand of
type
'const unsigned...
2007 May 31
4
[LLVMdev] Advice on a VStudio specific patch
...// these two together get me the unsigned < Edge operation
bool operator>(unsigned to) const {
return To > to;
}
friend bool operator<(unsigned to, const Edge& edge) {
return edge.operator>(to);
}
There is a similar set of additions for ScopedRange.
Adding the alternate comparitors and the return won't make things less
portable, but it does crudify the code somewhat in order to get around
the limitations of the compiler. Having a bunch of #ifdefs for VStudio
probably is crudier still, however. :-)
What do you think?
Thanks,
Chuck.
--...
2007 May 31
0
[LLVMdev] Advice on a VStudio specific patch
On Thu, 31 May 2007, Chuck Rose III wrote:
> Our project is cross platform and on Windows we use VStudio 2005.
> VStudio presents a couple of issues related around it's STL
> implementation and also it's non-respect for the no-return semantic of
> abort().
Ok. We want the source to be portable, so it's goodness to get these
fixes into the main tree.
> I've fixed
2007 May 31
2
[LLVMdev] Advice on a VStudio specific patch
Hola LLVMers,
Our project is cross platform and on Windows we use VStudio 2005.
VStudio presents a couple of issues related around it's STL
implementation and also it's non-respect for the no-return semantic of
abort().
I've fixed it locally, but I'd like to send a patch so I don't have to
do this every time I update from the source repository. So.... if I'm