similar to: [LLVMdev] Visual Studio 2010 build warning & errors

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,

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,  std::pairs or pointers are being constructed using a 0 > as an initializer causes an error inside the std::pair

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.aspx It even says: Casting the expression to type bool will not disable the warning, which is by design. On Thu, Sep 23, 2010 at 9:18 AM, Nathan Jeffords

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

For those that are interested, I have attached the latest version of my Win32 COFF support patch. There is no new functionality, I just fixed some compiler errors due to recent changes in the MC library. - Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100527/23598d23/attachment.html>

Hi guys, I have attached my patch to support generating win32 COFF object files. I would have posted earlier, but my system drive crashed and I had to rebuild my system; Luckily, my source code was on a secondary drive. I think this would be a good beginning for ongoing support of the COFF object file format and was hoping for some feedback as to whether it was commit worthy or what was needed to

Orestes Zoupanos wrote: > VS2015, considering it's quite recent and the Community Edition has a > free-to-use-for-open-source license going on. > >>> Yup, into win32\VS2010 and VS2015. >> >> VS2015 or VS2005? Currently FLAC has 2 Visual Studio solutions: one >> for VS2005 >> (and 2008) and another for VS2010 and all newer (2012, 2013, 2015...)

I checkout LLVM and clang from SVN, then use CMake to generate project files for Visual Studio 2010 (I started with 2008). The LLVM project compiles successfully and gives me all the tools including Clang. For a few tests, I compile C++ code with Clang which if I need to I link, I use MinGW's ld passing all the relevant object files and libraries including correctly ordering the start-up code

On Sun, Sep 26, 2010 at 3:28 PM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords > <blunted2night at gmail.com> wrote: > > Hi guys, > > While trying to get dwarf debugging information to work with Win32 COFF > > targets, I came across a couple of issues with the current implementation > > of

wrapping the macro's body in: do { ... } while (false) would make the the macro a proper statement so that: if (cond) ASSERT(some_other_cond); else do_something_cool (); compiles as expected. IMO, it would work as such #define ASSERT_STM(cond,expr) On Tue, Jul 26, 2011 at 6:36 PM, Reid Kleckner <reid.kleckner at gmail.com>wrote: > He wants to be able to resume execution

sorry, my previous message got sent too early I think the macro should look something like this: #define ASSERT_STRM(cond,expr) \ do { if (cond) { std::cerr << expr << std::end; assertion_trap (); } } while (false) On Tue, Jul 26, 2011 at 7:57 PM, Nathan Jeffords <blunted2night at gmail.com>wrote: > wrapping the macro's body in: > > do { ... } while

There are a variety of "real world situations," some of them would benefit from shared-library packaging and some would not. Say you're building a set of tools for internal deployment in your large-ish organization. Factoring out the Clang/LLVM bits into a shared library can reduce memory footprint when running multiple tools, reduce disk footprint which therefore reduces antivirus

Erik de Castro Lopo wrote: >> I'm looking to maybe move all the .sln and related Visual Studio project >> files (not the source .c and .h files!) into new directories under >> "win32\*" within the flac reppo. >> Any objections/tips or reasons to leave them as is? > > Lvqcl and other Windows devs? > > I'm ok with this if you are. I don't

Hi guys, While trying to get dwarf debugging information to work with Win32 COFF targets, I came across a couple of issues with the current implementation of WinCOFFObjectWriter. Emitting empty section causes debug information to invalid, as the presence of certain debug section implies available information, and emission of labels as symbols confused gdb about the structure of the program. The

Hi, I can build LLVM just with VS2010 x64. However, when I try to build it with -DBUILD_SHARED_LIBS:BOOL=true option, it seems to fail with a lot of unresolved external symbol. Is it a known issue? Is there anyway to fix it? Thanks, http://old.nabble.com/file/p31351142/build.log build.log -- View this message in context:

Download the Visual Studio Ultimate Trial here: http://www.microsoft.com/visualstudio/en-us/try Thanks, Michael -----Original Message----- From: rappard at gmail.com [mailto:rappard at gmail.com] On Behalf Of rappard at dds.nl Sent: Monday, March 12, 2012 9:47 AM To: Michael Scherotter Cc: flac-dev at xiph.org Subject: Re: [flac-dev] FLAC build for Visual Studio 2010? I'd be happy to test

On Sun, Sep 26, 2010 at 6:47 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > On Sun, Sep 26, 2010 at 3:28 PM, Michael Spencer <bigcheesegs at gmail.com> > wrote: >> >> On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords >> <blunted2night at gmail.com> wrote: >> > Hi guys, >> > While trying to get dwarf debugging information to work

Hi Carlo, Do you have VS2010 handy? It should read the DI fine. Unfortunately, VS2013 is not able to use the debug info we generate. It is on my plans to investigate and fix the generator, but I didn't have enough free cycles recently. -- Tim 2014-09-15 20:30 GMT+04:00 Reid Kleckner <rnk at google.com>: > +Timur > > Hm, this didn't work out of the box for me. > >

It seems to be that LLVM doesn't make sense as a shared library. The surface area of the interface is massive, and in constant flux. I would think in real world situations, a domain specific interface with a more focused public interface would the right solution. On Fri, Apr 6, 2012 at 6:15 PM, Alan Garny <agarny at hellix.com> wrote: > Hi,**** > > ** ** > > From what I

Great suggestion - what should the !NDEBUG version look like? On Tue, Jul 26, 2011 at 8:01 PM, Nathan Jeffords <blunted2night at gmail.com>wrote: > sorry, my previous message got sent too early > > I think the macro should look something like this: > > #define ASSERT_STRM(cond,expr) \ > do { > if (cond) { > std::cerr << expr << std::end; >