Displaying 5 results from an estimated 5 matches for "vc2k3".
Did you mean:
vc2k5
2008 Dec 07
0
[LLVMdev] Build errors on trunk for about a week now.
...includes, libs, defines, and
about ten other things, it is needed in every case, spent about 8
hours on all this so I am extremely sure). Attached is the patch;
should I post it to the LLVM list as well?
Oh, and yes, instead of VC2k5 being the minimum requirement, it should
be VC2k5SP1 (although VC2k3 does not have that issue, if someone
managed to get around to fixing the friend errors that VC2k3 is bugged
with).
Actually, I am forwarding this to the list anyway, good record in case
anyone searches.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FunctorPatc...
2008 Dec 05
4
[LLVMdev] Build errors on trunk for about a week now.
I did some looking up on that const thing. Apparently that const is
'supposed' to be there, but it is not strictly required. However
there is a bug in VS2k3 (VS7) through VS2k8 (VS9) (no clue if it has
been fixed yet) that requires it to be there when the functor is being
called through a const qualified interface, such as through stl
containers. They state that a bug report has been
2008 Oct 11
0
[LLVMdev] 2.4 Pre-release (v1) Available for Testing
On Oct 10, 2008, at 1:44 PM, Óscar Fuentes wrote:
> OvermindDL1 <overminddl1 at gmail.com> writes:
>
> [snip]
>
>> On this first compile everything compiled except for llc and lli,
>> which did not link due to:
>> unresolved external symbol "class llvm::FunctionPass * __cdecl
>> llvm::createPBQPRegisterAllocator(void)"
>
> That is because
2008 Oct 10
8
[LLVMdev] 2.4 Pre-release (v1) Available for Testing
OvermindDL1 <overminddl1 at gmail.com> writes:
[snip]
> On this first compile everything compiled except for llc and lli,
> which did not link due to:
> unresolved external symbol "class llvm::FunctionPass * __cdecl
> llvm::createPBQPRegisterAllocator(void)"
That is because the lib/CodeGen project file is missing PBQP.cpp.
[snip]
> On Fri, Oct 10, 2008 at 2:11
2008 Oct 11
4
[LLVMdev] 2.4 Pre-release (v1) Available for Testing
...etration on Windows, for instance, is
> almost nil. Is it really worth the trouble to support things like
> testing on systems that almost nobody (wants to) use?.
Well I use it, and I know of three other windows LLVM users that have
contacted me for help with their own projects as well. The VC2k3
support is broken because of a "friend" declaration in LLVM in a way
that VS2k3 does not support (2k3's fault, although the friend usage
was also questionable...).
Although I think the main lack of visible Windows users (there are
definitely Windows llvm users) is because llvm feels...