similar to: [LLVMdev] Advice

Just got clang from head and getting: ExprConstant.cpp: In function Obool TryEvaluateBuiltinNaN(clang::ASTContext&, clang::QualType, const clang::Expr*, bool, llvm::APFloat&)¹: ExprConstant.cpp:1578: error: no matching function for call to Ollvm::StringRef::getAsInteger(int, llvm::APInt&)¹ /home/neale/LLVM/llvm/include/llvm/ADT/StringRef.h:269: note: candidates are: bool

Hi, Were you able to get past this error: make[1]: Entering directory `/builddir/build/BUILD/llvm-2.5/lib/VMCore' llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td tblgen: IntrinsicEmitter.cpp:137: void EmitTypeForValueType(std::ostream&, llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' failed. make[1]: Leaving directory

I searched the archives and found this from last month: I ran into the same problem and fixed it by forcing the MVT::SimpleValueType enum to be 64 bits so that all of the types in the union later in the class are the same size. I tested this on ppc64 and x86_64. Index: include/llvm/CodeGen/ValueTypes.h =================================================================== ---

I have a Putty variant that works well with openSSH up until 7.4. After git bisecting I found that after the application of c38ea634893a1975dbbec798fb968c9488013f4a the client fails with host key mismatch. The commit in question appears to remove vestiges of ssh-1 support but my client is using 2.0. I am trying to work out what in that commit would lead to the symptoms. I have been through the

With the TableGen problem circumvented the build proceeds quite well up until: llvm[2]: Linking Debug executable llc /home/neale/LLVM/llvm/tools/llc/Debug/llc.o: In function `ForceCodegenLinking': /home/neale/LLVM/llvm/include/llvm/CodeGen/LinkAllCodegenComponents.h:45: undefined reference to `llvm::createBURRListDAGScheduler(llvm::SelectionDAGISel*, bool)'

I ran with VERBOSE=1 and see: g++ -I/home/neale/LLVM/llvm/include -I/home/neale/LLVM/llvm/tools/llc -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g -fno-exceptions -fPIC -Woverloaded-virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused -Wno-unused-parameter -g -Wl,-R -Wl,/home/neale/LLVM/llvm/Debug/bin -Wl,-export-dynamic

Hi, I am beginning the porting process for Linux on System z (aka IBM Mainframe). I thought I¹d build LLVM first with the c and cpp backends so that tools like TableGen would be created that I¹d then use to process the .td files that I¹ll be creating. So I used svn to grab the code from the repository and ran configure and make. However, the build breaks at this point: llvm[1]: Building

Hi, > llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td > tblgen: IntrinsicEmitter.cpp:163: void EmitTypeForValueType(std::ostream&, > llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' > failed. this came up before IIRC, but I don't remember the details - buggy system compiler? Try searching the archives. Also, if you

* Neale Ferguson: > So the SimpleTy variable which is a SimpleTypeValue is behaving strangely. > It's found within a private definition: > > union { > uintptr_t V; > SimpleValueType SimpleTy; > const Type *LLVMTy; > }; > > The comment in the above fix indicates that in this 64-bit system the enum > needs to be 64-bits is correct,

Hello, Neale > -lLLVMBitReader /home/neale/LLVM/llvm/Debug/lib/LLVMCBackend.o > -lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis > /home/neale/LLVM/llvm/Debug/lib/LLVMCppBackend.o -lLLVMTarget -lLLVMCore > -lLLVMSupport -lLLVMSystem -lpthread -ldl -lm -lelf It seems, that you did not specify any single backend except C. Please do so. > So it

I have written a managesieve server from scratch in Python. I did just enough work to get it working with avelsieve (the squirrelmail plugin), smartsieve, and KDE's sieve kioplugin. It supports the entire Internet draft. Since I didn't have a working sieve server to compare against, I'm not sure if it's 100% compatible with timsieved. Client applications seem to work okay

Hello, Neale > These entry points are in modules that have been compiled and placed into an > archive. (e.g. llvm::createBURRListDAGScheduler is in ScheduleDAGRRList.cpp > whose object is placed in ./Debug/lib/libLLVMSelectionDAG.a). > > I'm sure I've missed a configuration option or something trivial like that > but my newbie brain can't determine what it is. make

Hi, I just checked out llvm from svn and attempted to build the systemz + cpp targets. I am getting the following error: EDDisassembler.cpp:42:49: error: ../../lib/Target/X86/X86GenEDInfo.inc: No such file or directory Is that file which is generated as part of the build process? If so, I assume EDDisassembler shouldn't be compiled for a systemz build. Neale -------------- next part

Hi I''m new to Rails and I''m struggling with a ''has-one'' relationship. I''m trying to save product and image data in seperate tables with one to one relationship. I''m assuming the problem lies in the controller method below but can''t work it out. The models contain the has_one and belongs to statements, and I tried swapping these

Hi Neale, > The comment in the above fix indicates that in this 64-bit system the enum > needs to be 64-bits is correct, but the fix doesn't seem to do it. the basic problem seems to be that your system compiler is miscompiling LLVM. Mucking around with the details of the union in the hope of tricking the compiler into not miscompiling is one approach, but as you saw each broken

Hi, I'm testing Dovecot to migrate from my old Courier IMAP/POP server. It work fine but I have some problems to start the sieve server "pysieved" from Neale Pickett in PAM auth, I got the message: Traceback (most recent call last): File "/usr/share/pysieved/pysieved.py", line 97, in <module> main() File "/usr/share/pysieved/pysieved.py", line

I get these BIZARRE results from wilcox.test() When INCREASING the number of samples i get INCREASED p-values. When increasing the number of samples further, the p-values goes down again. This seems really bizarre! Can anyone explain why this is so?! Example: > w <- wilcox.test(c(1:40),(c(1:40)+100)) > w$p.value [1] 1.860340e-23 > w <- wilcox.test(c(1:50),(c(1:50)+100)) >

I'm trying to diagnose a bizarre problem in which the help files invoked from R are partially defective. help(), for instance, is missing the Description, Arguments and See Also sections; as are help files for other commands (see below). I've built 2.8.1, 2.10.1 and HEAD with the same results; do I need to set an environment or configuration variable? help

Hi Neale, > Yes, that works much better. However, I fear the problem is more to do with > trying to force enums to be a different size which appears not to be > supported by most compilers. The IBM C++ compiler apparently has a #pragma > which can be used to do it and gcc 4.3 seems to be happy with the hack > described but as Duncan says trying to force this behavior in a union is

This is going to look silly, but I've seen it asked so many times that I'm starting to think it should be included in the OpenSSH distribution. People want to set up persistent tunnels without having to keep a shell open. The following program can be used with -f to do just that: #include <unistd.h> int main() { pause(); return 0; } Any chance of this making it