search for: ahmedcharles

...; here are updated versions > > - Nathan > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > -- Ahmed Charles http://www.ahmedcharles.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100925/50fe257a/attachment.html>

On Thu, Sep 23, 2010 at 4:04 AM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Thu, Sep 23, 2010 at 2:40 AM, Nathan Jeffords > <blunted2night at gmail.com> wrote: > > here are a couple of patches to address some warnings > > in Microsoft compilers, and a build error in vs2010 in particular > > vs2010-errors.patch: > > In SelectionDAGISel,

Sorry, I should have checked the change to the patch. Here is a new patch that fixes it. I found a couple of more places with the same issue. -Nathan On Sat, Sep 25, 2010 at 7:53 AM, Ahmed Charles <ahmedcharles at gmail.com>wrote: > Note: static_cast<bool> doesn't make the warning go away or did you check > that? I just compiled a small test and it didn't work. The recommended > solution is: > > (expression) != 0 > > http://msdn.microsoft.com/en-us/library/b6801kcy.a...

So... Are 40 and 41 the only legal behaviors or are there more? Robby On Tuesday, April 19, 2011, Ahmed Charles <ahmedcharles at gmail.com> wrote: > This code is undefined, meaning that all bets are off, don't do it. > I.e. It reads the value of I between two sequence points and uses it > for something other than determining the value written. From: Csaba > Raduly > Sent: Tuesday, April 19, 2011 3:44...

...mail/cfe-dev/2010-August/010379.html >> > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -- Ahmed Charles http://www.ahmedcharles.com

This code is undefined, meaning that all bets are off, don't do it. I.e. It reads the value of I between two sequence points and uses it for something other than determining the value written. From: Csaba Raduly Sent: Tuesday, April 19, 2011 3:44 AM To: Joe Armstrong Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Is this a bug in clang? Hi Joe On Tue, Apr 19, 2011 at 10:59 AM, Joe

On Mar 9, 2011, at 2:32 AM, Olaf Krzikalla <Olaf.Krzikalla at tu-dresden.de> wrote: > Hi @llvm, > > Am 08.03.2011 20:14, schrieb Jakob Stoklund Olesen: >> Is that extra method getting called? What happens if you stick assert(0) in there? > That won't work either (that is, the assert fires). In debug mode the MSVC lib tries to test the ordering of the sequence. And it

...Make Error at include/clang/Basic/CMakeLists.txt:2 (tablegen): Unknown CMake command "tablegen". Call Stack (most recent call first): include/clang/Basic/CMakeLists.txt:9 (clang_diag_gen) -- Configuring incomplete, errors occurred! On Sat, Mar 20, 2010 at 5:34 PM, Ahmed Charles <ahmedcharles at gmail.com> wrote: > On Sat, Mar 20, 2010 at 10:13 AM, Russell Wallace > <russell.wallace at gmail.com> wrote: >> Ah, okay, thanks. Is the same true of Clang? >> > > Clang builds with MSVC, though to build something you have to have a > 'gcc' in your pa...

On Sat, Mar 20, 2010 at 10:13 AM, Russell Wallace <russell.wallace at gmail.com> wrote: > Ah, okay, thanks. Is the same true of Clang? > Clang builds with MSVC, though to build something you have to have a 'gcc' in your path to build the assembly that is produced.

Hi @llvm, Am 08.03.2011 20:14, schrieb Jakob Stoklund Olesen: > Is that extra method getting called? What happens if you stick assert(0) in there? That won't work either (that is, the assert fires). In debug mode the MSVC lib tries to test the ordering of the sequence. And it uses the yielded predicate for this (which in this particular case is a very bad idea). > I hoped the

Sorry, always end up not replying to the list: The main issue with dealing with next this way is that people adding new uses of next will probably not be using c++0x and therefore won't know it's ambiguous and that it needs to be qualified. There are also two issues with rvalue references and the STL: 1. EquivalenceClasses, in the insert and findLeader functions, it uses map functions

On Fri, Feb 19, 2010 at 9:14 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > On Friday 19 February 2010 19:33:32 james woodyatt wrote: > > Let us all now give a warm welcome to our new Haskell comrades! > > Hopefully Mono will be next. > Mono has already used LLVM for various things. -------------- next part -------------- An HTML attachment was scrubbed... URL:

> +  // Helper for test code to print hash codes. > +  void PrintTo(const hash_code &code, ::std::ostream *os) { > > What's with the extra leading :: before std::? Have you ever tried: namespace foo { class std {}; } using namespace foo; #include <vector> Well, I'm not sure that Chandler is guarding against this possibility, but most library implementations of the

Technically, it could've sent the mail before you even thought about writing it. Undefined is undefined, there are no requirements. From: Dustin Laurence Sent: Wednesday, April 20, 2011 6:50 AM To: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Is this a bug in clang? On 04/19/2011 10:50 PM, John Regehr wrote: > The compiler is perfectly within its rights to send a rude email to your >

Note: /Za shouldn't be used. P.S. I'd say more, but it'd only water down the message. ------------------------------ From: Nikola Smiljanic Sent: 9/30/2011 12:45 AM To: Bryce Cogswell Cc: cfe-dev; llvmdev Subject: Re: [LLVMdev] [cfe-dev] Unicode path handling on Windows I tried to do the conversion to lowercase inside GetFullPath by adding an additional bool parameter to this