search for: pacifist

Displaying 9 results from an estimated 9 matches for "pacifist".

2012 May 29
3
[LLVMdev] make error
...atus: executing tools/Makefile commands config.status: executing tools/sample/Makefile commands and make outputs make ENABLE_OPTIMIZED=1 VERBOSE=1 llvm llvm[0]: Constructing LLVMBuild project information. /home/pacifist/research_documents/LLVM_Play/using_directions/llvm/utils/llvm-build/llvm-build \ --native-target "x86" \ --enable-targets "X86 Sparc PowerPC ARM Mips CellSPU XCore MSP430 CppBackend MBlaze NVPTX Hexagon" \ --enable-optional-components "" \ --write-library-table...
2012 May 29
0
[LLVMdev] make error
....status: executing tools/Makefile commands > config.status: executing tools/sample/Makefile commands > > and make outputs > > make ENABLE_OPTIMIZED=1 VERBOSE=1 > llvm > llvm[0]: Constructing LLVMBuild project information. > /home/pacifist/research_documents/LLVM_Play/using_directions/llvm/utils/llvm-build/llvm-build > \ > --native-target "x86" \ > --enable-targets "X86 Sparc PowerPC ARM Mips CellSPU XCore MSP430 > CppBackend MBlaze NVPTX Hexagon" \ > --enable-optional-components "" \ &...
2006 May 16
7
svn-1.3.1 errors on intel mac on checkout
I just installed svn-1.3.1 from .dmg on an intel mac. I am getting ... subversion/libsvn_wc/log.c:338: (apr_err=155009) svn: In directory ''sr'' subversion/libsvn_subr/io.c:565: (apr_err=2) svn: Can''t copy ''sr/.svn/tmp/text-base/README.svn-base'' to ''sr/README.tmp'': No such file or directory Any one getting this? TIA for any help.
2009 May 21
4
gdi32.dll error
Hello, I encounter the same problem on MacOSX 10.5.6, either using X11 supplied with Leopard, or X11 2.3.3.2 (XQuartz) and Xcode 3.1.2. It appears using Darwine 1.1.21 from Kronenberg, Darwine 1.1.7 from thisismyinter.net, or the lastest wine-1.1.21, compiled from source. The only way to use wine is to installed wine stable from MacPorts or the Kronenberg's 1.1.21. Hardly, it
2007 Oct 15
14
Top Quoting?
Sort of off-topic and don''t mean to complain, but many on this list use top quoting. That works ok if you don''t quote the whole previous thread. However, I''m finding that scrolling forever to locate the reply on longer threads is getting tedious. What''s the rationale for top-quoting? Thx.
2012 Aug 23
0
[LLVMdev] [PATCH] Fix for bug in JIT exception table allocation (no test yet)
...chaelMuller = mmuller at enduden.com | http://www.mindhog.net/~mmuller ----------------------------------------------------------------------------- The people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same way in any country. - Hermann Goering (Hitler's right-hand man) =============================================================================
2007 Sep 03
1
FLAC_index
Hi, Christian Weisgerber <naddy@mips.inka.de> wrote: > I guess the use of unsigned index variables was an accident. Changing > them back to int makes FLAC pass the "thorough" test suite on amd64. I was wondering why there isn't a FLAC_index (FLAC_index16 or FLAC_index32) type that would prevent someone from just "winging" it with a bad choice for an index to
2012 Aug 21
2
[LLVMdev] [PATCH] Fix for bug in JIT exception table allocation (no test yet)
Hi, I found a bug in the code that generates exception tables, I've attached what I think is the correct fix. When you run out of space writing to a buffer, the buffer management code simply stops writing at the end of the buffer. It is the responsibility of the caller to verify that it has stayed in bounds and perform a retry with a larger memory estimate if not. The function writing code
2012 Aug 22
1
[LLVMdev] [PATCH] Fix for bug in JIT exception table allocation (no test yet)
On Aug 21, 2012, at 2:12 PM, Michael Muller <mmuller at enduden.com> wrote: > > Hi, I found a bug in the code that generates exception tables, I've attached > what I think is the correct fix. > > When you run out of space writing to a buffer, the buffer management code > simply stops writing at the end of the buffer. It is the responsibility of > the caller to