Displaying 20 results from an estimated 900 matches similar to: "[LLVMdev] Visual C++ Toolkit"
2004 Jul 08
0
[LLVMdev] Visual C++ Toolkit
On Thu, 8 Jul 2004, Bill Wendling wrote:
> I just wanted to know if anyone's looked into using the free version of
> Microsoft's Visual C++ toolkit for LLVM:
>
> http://msdn.microsoft.com/visualc/vctoolkit2003/
Sorry, but it is not even close to working (its template and STL support
is horribly lacking). The Visual Studio "Whidbey" compiler, now in beta,
will
2004 Jul 08
3
[LLVMdev] Visual C++ Toolkit
Chris Lattner wrote:
> On Thu, 8 Jul 2004, Bill Wendling wrote:
> > I just wanted to know if anyone's looked into using the free version of
> > Microsoft's Visual C++ toolkit for LLVM:
> >
> > http://msdn.microsoft.com/visualc/vctoolkit2003/
>
> Sorry, but it is not even close to working (its template and STL support
> is horribly lacking). The
2004 Jul 08
1
[LLVMdev] Visual C++ Toolkit
Hi,
Have you tried the new VC8 Beta? It's been out for less than 2 weeks:
http://lab.msdn.microsoft.com/express/visualc/default.aspx
It's supposed to have improved standards compliance.
Regards,
-Eugene Talagrand
On Thu, 8 Jul 2004, Chris Lattner wrote:
> Date: Thu, 08 Jul 2004 01:56:03 -0500 (CDT)
> From: Chris Lattner <sabre at nondot.org>
> Reply-To: llvmdev at
2004 Jul 08
0
[LLVMdev] Visual C++ Toolkit
On Thu, 8 Jul 2004, Vladimir Prus wrote:
> > Sorry, but it is not even close to working (its template and STL support
> > is horribly lacking). The Visual Studio "Whidbey" compiler, now in beta,
> > will handle it though with only a reasonable amount of tweaking to the
> > LLVM sources. I have no idea about when Microsoft intends to release it
> > though,
2004 May 19
4
Microsoft Visual C++ available for zero cost
I just found this:
http://msdn.microsoft.com/visualc/vctoolkit2003/
I don''t tend to pay much attention to Microsoft and MS Windows, so
perhaps everyone else already knew about it. Basically, they have
released a command-line-only version of their C++ compiler and libraries
for free (gratis) downloading.
I assume this version would be able to compile wxRuby, but would be
2004 Apr 26
1
[LLVMdev] Multiple Returns
Hi all,
Quick question: What is the best way to have multiple return values from
a function? Would that be placing these into a structure and returning
that to the caller?
Thanks.
-bw
--
|| "If wishes and buts were clusters of nuts, we'd all have a bowl of
|| granola!" - Mr. Jellineck
2004 Aug 03
0
[LLVMdev] Compiler Driver [high-level comments]
Chris Lattner wrote:
} > I tend to agree. I'm a strong advocate of XML myself (on other
} > projects). However, introducing XML would make LLVM dependent on some
} > kind of XML parser. We could probably get away with expat (small, fast)
} > for our purposes in LLVM, but there is still the issue of dependency. To
}
} To me, it's not a matter of "one more
2004 Sep 02
0
[LLVMdev] Type uint64_t required but not found
Henrik Bach wrote:
} Hi John,
}
} configure still exits, when checking for uint64_t. I've attached a patch,
} that properly will fix it. Either uint64_t or u_int64_t will succeed:
}
} Index: configure.ac
} ===================================================================
} RCS file: /var/cvs/llvm/llvm/autoconf/configure.ac,v
} retrieving revision 1.106
} diff -u -r1.106 configure.ac
} ---
2004 Aug 03
2
[LLVMdev] Compiler Driver [high-level comments]
On Mon, 2 Aug 2004, Reid Spencer wrote:
> Hi Bill,
> On Mon, 2004-08-02 at 21:31, Bill Wendling wrote:
> > Hi Reid,
> >
> > > Since there's been little feedback on the design document I sent out,
> > > some decisions are being made in order to progress the work. If you have
> > > strong feelings about any of these, voice them now!
> > >
2004 Sep 02
2
[LLVMdev] Type uint64_t required but not found
Hi John,
configure still exits, when checking for uint64_t. I've attached a patch,
that properly will fix it. Either uint64_t or u_int64_t will succeed:
Index: configure.ac
===================================================================
RCS file: /var/cvs/llvm/llvm/autoconf/configure.ac,v
retrieving revision 1.106
diff -u -r1.106 configure.ac
--- configure.ac 2 Sep 2004 18:44:44 -0000
2004 Aug 18
2
[LLVMdev] Meet The Developers
LLVM Developers,
We've added a page to the main web site that provides links to each LLVM
Developer's home page and/or personal LLVM Notes page. You can find it
here: http://llvm.org/Developers.html or just click the link titled
"LLVM People" on the left of the main page.
The list isn't complete but contains pictures and links for everyone
that responded in IRC this morning
2004 Mar 26
2
[LLVMdev] Extending LLVM
Hi all,
I had a quick question. I think it's possible to do this, but just
wanted to make sure.
It is possible to extend LLVM to add, say, matrix operations at a higher
level and then "lower" them into some version of LLVM "proper" after
performing any transformations on them, right? Also, it's possible to
have any custom-made types (like "matrix") as well?
2004 Aug 03
2
[LLVMdev] Compiler Driver [high-level comments]
Hi Reid,
> Since there's been little feedback on the design document I sent out,
> some decisions are being made in order to progress the work. If you have
> strong feelings about any of these, voice them now!
>
> 1. Name = llvmcc
I like llvmcc, but really have no strong opinion.
> 2. The config file format will resemble Microsoft .ini files
> (name=value in
2005 Feb 18
0
[LLVMdev] LLVM built on VS C++ 2005
> GCC is smart enough to realize it doesn't return. That's because the
> declaration of abort() is decorated with __attribute__((__noreturn__)).
>
> So is GCC smarter than VC++? As it turns out, in VC++ the declaration of
> abort() is decorated with __declspec(noreturn).
>
> Whidbey is not stricter than 2003, it is merely buggier. VC++ has always
> complained
2005 Feb 18
3
[LLVMdev] LLVM built on VS C++ 2005
GCC is smart enough to realize it doesn't return. That's because the
declaration of abort() is decorated with __attribute__((__noreturn__)).
So is GCC smarter than VC++? As it turns out, in VC++ the declaration
of abort() is decorated with __declspec(noreturn).
Whidbey is not stricter than 2003, it is merely buggier. VC++ has
always complained about functions failing to return a
2004 Apr 08
3
[LLVMdev] Code documentation
Hello,
is there any documentation for LLVM codebase other than produced by doxygen?
The reason I'm asking is that doxygen docs are
(1) not very complete at the moment, as lot of classes don't even have a
description
(2) is generally not the best way to get high-level view of a big codebase.
As an example, consider this code:
%tmp.1 = setgt int %i, 0
br bool %tmp.1, label
2004 Sep 15
0
[LLVMdev] diffs for vc7.1
On Wed, 15 Sep 2004 19:51:08 +0200
Paolo Invernizzi <arathorn at fastwebnet.it> wrote:
>
> On Sep 15, 2004, at 7:29 PM, Jeff Cohen wrote:
>
> > Just make sure you read the uninstall instructions before installing.
> > Microsoft has been known to essentially require the reformatting your
> > boot partition in order to uninstall beta versions of VS. And, of
>
2004 Sep 15
1
[LLVMdev] diffs for vc7.1
On Sep 15, 2004, at 8:04 PM, Jeff Cohen wrote:
> I cannot find any specific instructions for uninstalling the VC++ 2005
> Express Edition. There is this README file:
> http://lab.msdn.microsoft.com/express/visualc/readme/default.aspx. As
> it isn't the full Visual Studio it probably isn't messing around with
> Windows system files.
>
> I do know for a fact that the
2003 Sep 10
1
[LLVMdev] Warning during compilation
Hi all,
I get this warning during compilation:
make[3]: Entering directory
`/home/wendling/llvm/llvm/lib/ExecutionEngine/JIT'
Compiling Emitter.cpp
Emitter.cpp:44:1: warning: "_POSIX_MAPPED_FILES" redefined
In file included from /usr/include/unistd.h:171,
from
/usr/include/c++/3.3.1/i586-mandrake-linux-gnu/bits/gthr-default.h:38,
from
2004 Sep 15
2
[LLVMdev] diffs for vc7.1
On Sep 15, 2004, at 7:29 PM, Jeff Cohen wrote:
> Just make sure you read the uninstall instructions before installing.
> Microsoft has been known to essentially require the reformatting your
> boot partition in order to uninstall beta versions of VS. And, of
> course, it is required that you uninstall the beta before installing a
> newer beta or the release version.
Urrggg! I