similar to: [LLVMdev] rantings about llvm-top

Displaying 20 results from an estimated 12000 matches similar to: "[LLVMdev] rantings about llvm-top"

2007 Aug 16
0
[LLVMdev] rantings about llvm-top
Hi Holger, On Thu, 2007-08-16 at 09:02 +0200, Holger Schurig wrote: > Hi Raid ! > > I used llvm-top at home and in the company and I basically I like > it. Thanks for trying it out! :) > Here are some comments: > > - the README.txt says that all routines use a common library > and therefore accept a common set of arguments. But this > is confusing, because
2007 Aug 16
1
[LLVMdev] rantings about llvm-top
> > - many directories are not svn:ignore'd in llvm-top, e.g. > > cfe, llvm-gcc-4.0, llvm. "svn st" shows you which one. > > Yeah, again, that's a module maintainer's issue. I can't be > cleaning up after everyone. People are just going to have to > learn how to use subversion properly. I try to fix things > where I find them, but there's
2012 Jan 02
7
Problem with detecting "Mustek PowerMust 2000VA"
Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver
2011 Apr 22
3
[LLVMdev] svn server permissions for top-level svn update
Hi, My svn working copy mirrors the layout of the whole svn repository, from llvm-project downwards, so I have: ~/svn/llvm-project/ ~/svn/llvm-project/llvm/ ~/svn/llvm-project/llvm/trunk/ # lots of stuff in here ~/svn/llvm-project/cfe/ ~/svn/llvm-project/cfe/trunk/ # and lots of stuff in here (and likewise for test-suite, llvm-gcc-4.2 and dragonegg) This is nice because I can do "svn
2003 Apr 23
3
top failure
Hello gentlemen, I've discovered an interesting failure on some machine running 4.7. It's so weird so I'd very unlikely notice it at all, but thanks to top(1): when launched, instead of displaying some useful figures it exits with an error: "top: nlist failed". >From quick look it appears that kvm_nlist() returns NULL for nlst[0].n_type. Strange, ignoring; next exit point
2007 Aug 30
1
[LLVMdev] [PATCH] enhance llvm-top
Hi Raid ! This patch fixes some issues with llvm-top: a) it always makes a debug build of llvm, even when OPTIMIZED="1" is in .options b) it now handles ASSERTIONS, CHECKING and DOXYGEN from .options, it handles DEBUG a bit (not much) better c) it adds support for THREAD After this patch there still is support missing for DEBUG. PROFILING, OPT_FOR_SIZE, STRIPPED missing. I
2007 Jul 02
2
[LLVMdev] Top Level Stuff
On Sun, 1 Jul 2007, Tanya M. Lattner wrote: > I don't think we should have a docs module. Its much better to allow a > person to check out only llvm and get the appropriate documentation. Same > for hlvm, and whatever project. Its very inconvenient to check out > multiple things just to get llvm and docs. To put it another way, I think the docs for the subproject should follow
2007 Jul 02
0
[LLVMdev] Top Level Stuff
On 2007-07-02, at 03:49, Chris Lattner wrote: > I think checking out llvm-project should give you something like this: > > mydir/llvm-project/ > llvm-config/* > README.txt > Makefile > > And probably nothing else. > > Importantly, the README.txt would talk about how to use the > makefile, suggesting
2007 Jul 02
2
[LLVMdev] Top Level Stuff
On Mon, 2 Jul 2007, Gordon Henriksen wrote: > As a possibly less-engineered complement, your end-state could be > provided simply by creating folders in Subversion prefabbed with > appropriate svn:externals. Make one for each end-project (llvm-gcc, > new-cfe, and soforth). It's not nearly so clever, but it might allow > initial usage much closer to the 'configure; make; make
2008 May 30
1
[LLVMdev] PATCH: clang: fix description for -Wimplicit-function-declaration
Currently, "clang -help" gives a strange output. This patch fixes it. -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-clang-warning.patch Type: text/x-diff Size: 610 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080530/1d2c5719/attachment.patch>
2010 Feb 12
8
[LLVMdev] Reminder: 2.7 code freeze in 1.5 weeks
On Feb 12, 2010, at 8:25 AM, David Greene wrote: > On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >> Just a reminder that the 2.7 code freeze is on Feb 21st. >> >> All major changes should be committed approximately 1 week before the code >> freeze to ensure adequate testing. Please do your part to keep the tree >> stable in the days leading up to the
2007 Aug 24
6
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
The web page "LLVM Link Time Optimization: Design and Implementation" contains errors. In the gray block below "Example of link time optimization" there are some source files and then a list of commands to execute: $ llvm-gcc4 --emit-llvm -c a.c -o a.o $ llvm-gcc4 -c main.c -o main.o $ llvm-gcc4 a.o main.o -o main 1) in current LLVM (e.g. llvm itself, cfe, llvm-gcc-4.0) no
2018 Apr 20
3
[cfe-dev] RFC: Implementing -fno-delete-null-pointer-checks in clang
On Wed, Apr 18, 2018 at 3:54 PM Tim Northover via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Despite the name, the flag actually has rather straightforward semantics > > from the compiler's perspective. From the gcc docs for > > -fdelete-null-pointer-checks: "Assume that programs cannot safely > > dereference null pointers, and that no code or data
2016 Mar 14
2
[cfe-dev] RFC: Proposing an LLVM subproject for parallelism runtime and support libraries
> I'd support some of Jame's comments if liboffload wasn't glued to OMP as it is now. I certainly have no objection to moving liboffload elsewhere if that makes it more useful to people. There is no real "glue" holding it there; it simply ended up in the OpenMP directory structure because that was an easy place to put it, not because that's the optimal place for it.
2016 Mar 14
6
[Openmp-dev] [cfe-dev] RFC: Proposing an LLVM subproject for parallelism runtime and support libraries
I think it would be great if StreamExecutor could use liboffload to perform its offloading under the hood. Right now offloading is handled in StreamExecutor using platform plugins, so I think it could be very natural for us to write a plugin which basically forwards to liboffload. If that worked out, we could delete our current plugins and depend only on those based on liboffload, and then all the
2010 Apr 19
2
[LLVMdev] Living on Clang
How about building this in the CMake or auto* level we build a separate build script for it? I attache a simple version here. It does seem to work here. It's a shell script, which uses cmake for the building but it seems the second stage file works. I am not really sure why a third stage is needed, but it can be added quite easily. A windows version should be trivial to write (next week). A
2018 Apr 19
3
[cfe-dev] RFC: Implementing -fno-delete-null-pointer-checks in clang
On 4/19/2018 11:48 AM, Manoj Gupta via llvm-dev wrote: > On Wed, Apr 18, 2018 at 12:54 PM Tim Northover > <t.p.northover at gmail.com <mailto:t.p.northover at gmail.com>> wrote: > > > On Wed, Apr 18, 2018 at 12:02 PM Friedman, Eli > <efriedma at codeaurora.org <mailto:efriedma at codeaurora.org>> wrote: > > > Despite the name, the
2011 Nov 04
5
Beating the Top-Posting Dead Horse
On Fri, Nov 4, 2011 at 12:44, BeeRich <beerich-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > As for top posting, that is an old school habit. Er, no it isn''t. You young punks wouldn''t know old-school if it bit you in the diapers! Now get off my lawn! ;-) Seriously though, REAL old-school quoting is interleaved point by point, with anything irrelevant trimmed
2013 Jan 08
6
[LLVMdev] ARM failures
The following failures are consistent on buildbot (and my local box). The Clang one I think it's assuming an Intel box, the other two look like the FileCheck are not good enough. http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4305 Clang :: CodeGen/compound-assign-overflow.c LLVM :: Transforms/LoopStrengthReduce/post-inc-icmpzero.ll LLVM ::
2007 Jul 02
0
[LLVMdev] Top Level Stuff
On 2007-07-02, at 13:56, Chris Lattner wrote: > On Mon, 2 Jul 2007, Gordon Henriksen wrote: > >> As a possibly less-engineered complement, your end-state could be >> provided simply by creating folders in Subversion prefabbed with >> appropriate svn:externals. Make one for each end-project (llvm-gcc, >> new-cfe, and soforth). It's not nearly so clever, but it