similar to: [LLVMdev] creating new llvm project?

On Mon, Aug 12, 2013 at 2:34 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > "Matthew O'Connor" <thegreendragon at gmail.com> writes: > > > I'm in the process of creating a new LLVM project based on the > instructions > > from http://llvm.org/docs/Projects.html. > > > > I have a bunch of questions: > > > > 1. What is the

"Matthew O'Connor" <thegreendragon at gmail.com> writes: > I'm in the process of creating a new LLVM project based on the instructions > from http://llvm.org/docs/Projects.html. > > I have a bunch of questions: > > 1. What is the relationship between CMake and the configure + Makefile > build systems for LLVM? If I intend to just use configure +

Hi, I'm attempting to do some alias analysis & other memory inspection. I've written a pointless AliasAnalysis pass (that says everything must alias) to attempt to verify that my pass is getting picked up & run by opt. I run opt with: opt -load ~/Applications/llvm/lib/MustAA.so -must-aa -aa-eval -debug < trace0.ll I see my pass being initialized, but never being called (I see

Commit-ID: 4a84d61a24296b8253b3f8f7c86ee28df53e2f3b Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=4a84d61a24296b8253b3f8f7c86ee28df53e2f3b Author: David S. Miller <davem at davemloft.net> AuthorDate: Wed, 17 Aug 2011 09:31:17 +0800 Committer: maximilian attems <max at stro.at> CommitDate: Mon, 2 Jul 2012 10:46:37 +0200 [klibc] [SHELL] Allow building

Hi Matthew, Did you add your alias analysis pass initializeEverythingMustAliasPass() into llvm::initializeAnalysis(PassRegistry &Registry) {} ? This will initialize it linked into the Analysis library. thanks, chen On Apr 28, 2014, at 8:43 PM, Jingyue Wu <jingyue at google.com> wrote: > > > > On Thu, Apr 24, 2014 at 4:38 PM, Matthew O'Connor <thegreendragon at

On Tue, Aug 27, 2013 at 3:32 PM, Eric Christopher <echristo at gmail.com>wrote: > Then which build system likely doesn't matter for you? > I'd like to take advantage of the build work that LLVM has done so that we don't have to spend as much time maintaining our build when we can just mimic LLVM's + we'd get the build support for how tools, libraries, includes,

This patch set if my first attempt to make virtio_console usable on s390. To do so, I had to change hvc_console, because s390 has no request_irq and no free_irq. I want to get feedback from the main users of hvc_console before I proceed. The basic idea of this patch set is to remove the calls to request_irq and free_irq and replace them with backend specific callbacks. Please see the

This patch set if my first attempt to make virtio_console usable on s390. To do so, I had to change hvc_console, because s390 has no request_irq and no free_irq. I want to get feedback from the main users of hvc_console before I proceed. The basic idea of this patch set is to remove the calls to request_irq and free_irq and replace them with backend specific callbacks. Please see the

Commit-ID: 6dc1db1bce863f0e0e0abda1b9a58d8cb22863ca Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=6dc1db1bce863f0e0e0abda1b9a58d8cb22863ca Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 19 May 2018 02:39:43 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: var: Set IFS to

Hey Rusty, This series adds support for generic ports with each port getting two vqs: one for input and one for output. The host notifies us via the config space of the max. number of ports that can be added for a particular device. As a result of that change, the buffer management for find_readbufs and send_bufs is moved to the vqs. Only one outbuf per port is used so we bide away some time in

Hey Rusty, This series adds support for generic ports with each port getting two vqs: one for input and one for output. The host notifies us via the config space of the max. number of ports that can be added for a particular device. As a result of that change, the buffer management for find_readbufs and send_bufs is moved to the vqs. Only one outbuf per port is used so we bide away some time in

Hello. I am running 0.3.6 compiz under Fedora Core 6 and nvidia 1.0-9631 binary driver. I have noticed that switching to console with ctrl-alt-f1 and then back to x with ctrl-alt-f7 locks up the system with a black screen more or less (sometimes the lockup is complete, sometimes the cursor moves and it is possible to switch back to console), A user on nvnews forums suggest that disabling sync to

This makes the Xen console just work. Before, you had to ask for it on the kernel command line with console=hvc0 Signed-off-by: Markus Armbruster <armbru at redhat.com> --- diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 49e5358..df63185 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -25,6 +25,7 @@ #include <linux/mm.h> #include

https://bugs.freedesktop.org/show_bug.cgi?id=51809 Bug #: 51809 Summary: jReality "Export->Image" on nouveau corrupts memory / locks up X server Classification: Unclassified Product: Mesa Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW

Hi folks! I'm trying to get rid of any dependency on libgcc*, but without success so far. The following commands were executed on a freshliy installed and updated Ubuntu 16.04 LTS: === snip === sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed sudo mv /usr/local /usr/local.orig git clone https://github.com/llvm/llvm-project.git cd llvm-project; git

Thus wrote David Demelier via llvm-dev: > Also you will need to add more options to the components. See for example: > > LIBCXX_CXX_ABI=libcxxabi > LIBCXX_USE_COMPILER_RT=On > LIBCXXABI_USE_LLVM_UNWINDER=On > LIBCXXABI_USE_COMPILER_RT=On > LIBCXX_HAS_GCC_S_LIB=Off > LIBUNWIND_USE_COMPILER_RT=On > > And as mentioned above > > CLANG_DEFAULT_CXX_STDLIB=libc++

Hi All, I am trying to build the 'lld' linker on Mac OS 10.9, but during the build, I am getting the errors. Following are the steps that I have followed: 1.     I have downloaded the ‘llvm-stable’ source code from the following location:   https://github.com/llvm-mirror/llvm/tree/stable   2.     Machine details(on which llvm source code isbeing built) are as follows: $ sw_vers

On Mon, Aug 12, 2013 at 2:22 PM, Matthew O'Connor <thegreendragon at gmail.com> wrote: > On Mon, Aug 12, 2013 at 2:34 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: >> >> "Matthew O'Connor" <thegreendragon at gmail.com> writes: >> >> > I'm in the process of creating a new LLVM project based on the >> > instructions

On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > This file is for configure+make build, not CMake, so I'm not sure why > > it's being included into your build (these failures aren't > > reproducible for me). > > Can you please list the exact steps you're doing to build

On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > This file is for configure+make build, not CMake, so I'm not sure why > it's being included into your build (these failures aren't > reproducible for me). > Can you please list the exact steps you're doing to build LLVM with > CMake and make sure you don't have additional CFLAGS (LDFLAGS etc)