Displaying 5 results from an estimated 5 matches for "comparitors".
Did you mean:
comparators
2007 May 31
4
[LLVMdev] Advice on a VStudio specific patch
...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.
-----Original Message-----
From: llvm...
2007 Jul 25
0
[LLVMdev] Fwd: Segment Register Use
...ry position is commonly either assigned as the base
pointer for the requested data structure or code offset.
Code is compiled for local memory values (static) relative cs and
known memory locations for the data in the modular process (ds)
.....
Here the model becomes critical:
In complex vector comparitors, high dimension math, and dense data
sets (with potentially distributed media storage being loaded), a
limited processor has few options (ia for now).
To compare characteristics of 2 or more "vectors" and write the result
to a new data container, it needs obvious access to these location...
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 Jul 25
3
[LLVMdev] Segment Register Use
I realize I am one of the few who uses the segment registers
(especially CS and DS) on the ia32 chips for example, and a definite
few with complete segregation models that rival specialized physical
processors...
GCC still fails to use these correctly and if your LLVM still depends
on either Generic or some of the RTL models they use in various
processor definitions, I express concern for
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