similar to: [LLVMdev] Support for Visual Studio 2008

Dio <dio.rahman at gmail.com> writes: [snip] > PS. I have a hard time to make the project compiled by MSVC 2008 -- > eventhough it is smoothly compiled by MSVC 2005 Have you tried cmake? http://llvm.org/docs/CMake.html -- Oscar

> Have you tried cmake? > > http://llvm.org/docs/CMake.html Yes! Of course! :-) I have configured the cmake to create VS 2008 solution. But , it is failed. Dio

For my money: variadic templates and some bug I hit when trying to use forward_as_tuple. On Aug 18, 2014 4:02 PM, "Aaron Ballman" <aaron at aaronballman.com> wrote: > On Mon, Aug 18, 2014 at 6:54 PM, Chris Bieneman <beanz at apple.com> wrote: > > I’d like to propose raising the minimum required compiler for the LLVM & > Clang trunks for Visual Studio to MSVC

Dear List Users Greetings, i have come across the problem where CentOS 6.3 x64 has more than 700 processes running. i am not sure where to start, what in normal or abnormal. [root at jet]# ps -A PID TTY TIME CMD 1 ? 00:00:03 init 2 ? 00:00:00 kthreadd 3 ? 00:00:00 migration/0 4 ? 00:00:00 ksoftirqd/0 5 ? 00:00:00 migration/0 6

On Fri, Aug 22, 2014 at 5:49 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 22 August 2014 00:48, Aaron Ballman <aaron at aaronballman.com> wrote: >> We told the community less than nine months ago (when we made the >> C++11 switch) that we would support the last two versions of MSVC. Now >> we're saying "only the latest version, because it has

On Mon, Dec 3, 2012 at 8:08 PM, Gordon Keiser <gkeiser at arxan.com> wrote: > As an update to this: > http://connect.microsoft.com/VisualStudio/feedback/details/769222/cl-exe-ice-when-building-llvm-trunk-at-o2 > > Microsoft has reproduced the ICE, given a workaround, and is planning a fix for a future MSVC release. I know not a lot of people are building with VS, but it's

I'm currently using MSVC 2012, but I saw that Alp Toker landed a patch to LLD to make it compile with MSVC 2013, so I believe it's doable. Update and try again. On Fri, Nov 15, 2013 at 11:49 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > I think I removed all uses of ErrorOr<void>. Can you try updating? > > On 15 November 2013 12:09, Daniel Albuschat

On Tue, 02 Nov 2004 10:25:39 +0100 "Henrik Bach" <henrik_bach_llvm at hotmail.com> wrote: > I've come over an open source script which should be able to convert unix > (gnu?) like makefiles to nmake. However, It possible needs some changes to > work with the llvm makefile framework. I'm very doubtful this utility is of any use. nmake is useless compared to gnu

+1 for 2013. The feature set is worth it. I expect that there will still be major incompatibilities around initializer lists, so I would avoid them unless you have MSVC or are OK with diagnosing the problem from a buildbot. On Tue, Aug 19, 2014 at 11:12 AM, Renato Golin <renato.golin at linaro.org> wrote: > I just broke a build by committing initializer list and a few other > C++11

Hi, Is there any way to debug the codeview output of llvm from within Visual Studio? I want to use the codeview line info debug output of clang/llvm. I tried with the x86_64-pc-windows-msvc and i686-pc-windows-msvc triples and linking it into an existing project with VC++ from within the IDE and outside with link /debug. Neither option lets me debug with Visual Studio as debugger host.

I’d like to propose raising the minimum required compiler for the LLVM & Clang trunks for Visual Studio to MSVC 2013. Doing this will allow us to take advantage of a bunch of C++11 features that are not supported by MSVC 2012. According to MSDN (http://msdn.microsoft.com/en-us/library/hh567368.aspx) the list is: * Non-static data member initializers * Variadic templates * Initializer lists *

I've come over an open source script which should be able to convert unix (gnu?) like makefiles to nmake. However, It possible needs some changes to work with the llvm makefile framework. Until then, I strongly suggest a repository for the msvc project files until we'll come with a lasting solution. It is natural that we, msvc guys, should keep these files in shape. Henrik.

On Thu, Aug 21, 2014 at 4:35 PM, Chris Bieneman <beanz at apple.com> wrote: > This thread hasn’t had too much traffic, but it sounds like many people are > in favor and there is no strong opposition. If I understand Aaron’s only > objection was based on preserving existing policy rather than a technical > reason. > > Anyone want to make the official call? > > -Chris

Hi, I understand that making lld's error message compatible with MSVC makes it easy to use in IDEs. But at the same time I personally prefer the current style of lld's error message because it's easier to read particularly when filenames or symbol names are long (which is a norm in modern projects). I'd start with experimenting your idea with a small change. I guess that the

Hi, this is about an issue newer kernels show, bysplitting direct I/O requests into 4k pieces to directly merge them in the Block Device Layer afterwards. If anyone is interested in own tests just use a simple command like dd if=/mnt/test/test-dd1 of=/dev/null iflag=direct bs=64k count=1 in combination with blktrace. The following patch is more a proposal for discussion than a solution, well

Hi, We would like to see that change, too, especially for lld/ELF. Chris, do you have a patch or just looking for help? Best Regards, Igor Kudrin C++ Developer, Access Softek, Inc. ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> Sent: Friday, February 23, 2018 6:37 AM To: Chris

On Mon, Nov 24, 2008 at 8:18 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > OvermindDL1 <overminddl1 at gmail.com> writes: > >>> Chris proposed on IRC to remove the Visual Studio project files and turn >>> CMake into the "standard" for building LLVM with VC++. >>> >>> If you have strong arguments against this, please voice them.

On 04/12/2012 06:29, Michael Spencer wrote: > On Mon, Dec 3, 2012 at 8:08 PM, Gordon Keiser <gkeiser at arxan.com> wrote: >> As an update to this: >> http://connect.microsoft.com/VisualStudio/feedback/details/769222/cl-exe-ice-when-building-llvm-trunk-at-o2 >> >> Microsoft has reproduced the ICE, given a workaround, and is planning a fix for a future MSVC release.

> On Behalf Of Nicholas Chapman > > On 04/12/2012 06:29, Michael Spencer wrote: > > On Mon, Dec 3, 2012 at 8:08 PM, Gordon Keiser <gkeiser at arxan.com> > wrote: > >> As an update to this: > >> http://connect.microsoft.com/VisualStudio/feedback/details/769222/cl- > >> exe-ice-when-building-llvm-trunk-at-o2 > >> > >> Microsoft

This idea is from ext4. By this patch, we can make the dio write parallel, and improve the performance. We needn''t worry about the race between dio write and truncate, because the truncate need wait untill all the dio write end. And we also needn''t worry about the race between dio write and punch hole, because we have extent lock to protect our operation. I ran fio to test the