search for: printattributes

...source transformation in llvm from c++11 more basic c++ (to transform away auto etc.) using llvm3.1. I generate llvm bitcode using "clang++ -emit-llvm ...", but executing llc -march=cpp throws /home/broes/software/llvm/lib/Target/CppBackend/CPPBackend.cpp:493: void {anonymous}::CppWriter::printAttributes(const llvm::AttrListPtr&, const string&): Assertion `attrs == 0 && "Unhandled attribute!"' failed. Does this point to some unimplented feature of the transformation? thanks in advance, Broes -------------- next part -------------- An HTML attachment was scrubbed... U...

I'm trying to load the apple attributes and classes to samba4 using ldbmodify. I can get it to load, sort of. I keep getting errors and having to modify the file. Command I'm using: sudo ldbmodify -v -H ldap://lda.server.local -UAdministrator /home/user/apple-mcx.ldif here is the ldif that I'm loading

...in CPPBackend.cpp deprecated or should those attributes be handled somehow in C++ code generation (which means that the previous attribute list should be added to the AttrKind enum of the Attribute class)? Cheers, -- Harris Bakiras llc: CPPBackend.cpp:521: void {anonymous}::CppWriter::printAttributes(const llvm::AttributeSet&, const string&): Assertion `!attrs.hasAttributes() && "Unhandled attribute!"' failed. 0 llc 0x00000000010edc22 llvm::sys::PrintStackTrace(_IO_FILE*) + 34 1 llc 0x00000000010ed049 2 libpthread.so.0 0x00007f9701addc...

.... I think with the new attributes API there should be a general solution that doesn't require handling specific attributes explicitly, though I may be wrong. - David > > Cheers, > > -- > > Harris Bakiras > > llc: CPPBackend.cpp:521: void > {anonymous}::CppWriter::printAttributes(const llvm::AttributeSet&, const > string&): Assertion `!attrs.hasAttributes() && "Unhandled attribute!"' > failed. > 0 llc 0x00000000010edc22 llvm::sys::PrintStackTrace(_IO_FILE*) > + 34 > 1 llc 0x00000000010ed049 > 2 libpt...

...) using llvm3.1. >> > I generate llvm bitcode using "clang++ -emit-llvm ...", but executing >> > llc >> > -march=cpp throws >> > /home/broes/software/llvm/lib/Target/CppBackend/CPPBackend.cpp:493: >> > void >> > {anonymous}::CppWriter::printAttributes(const llvm::AttrListPtr&, const >> > string&): Assertion `attrs == 0 && "Unhandled attribute!"' failed. >> > >> > Does this point to some unimplented feature of the transformation? >> Yes, but it seems irrelevant to your task. CPP backe...

...e has been updated to match the current code in 2.7.0 alpha. I just assumed that it is copied verbatim without checking because it says so in the sentence above the code ("As a more comprehensive example of constructing an R call in C code and evaluating, consider the following fragment of printAttributes in src/main/print.c.") I don't understand, however, what you mean by stating that USE_RINTERNALS is not needed (and I have to admit that I have no knowledge of this 'write-barrier checking' mechanism.) May I ask you to have a look at the following code snippet? --8<-- file...

But it is not taken 'verbatim from src/main/print.c' (at least not in that version of R), and the code is not run with USE_RINTERNALS defined when write-barrier checking is enabled. The example has been updated to match the current code in 2.7.0 alpha. On Sun, 30 Mar 2008, sanders at fs.tum.de wrote: > Full_Name: Simon Anders > Version: 2.6.2 > OS: Ubuntu Linux >

...t || I->getKindAsEnum() == Attribute::Naked || diff --git a/lib/Target/CppBackend/CPPBackend.cpp b/lib/Target/CppBackend/CPPBackend.cpp index f610fbb..5589f69 100644 --- a/lib/Target/CppBackend/CPPBackend.cpp +++ b/lib/Target/CppBackend/CPPBackend.cpp @@ -510,6 +510,7 @@ void CppWriter::printAttributes(const AttributeSet &PAL, HANDLE_ATTR(StackProtect); HANDLE_ATTR(StackProtectReq); HANDLE_ATTR(StackProtectStrong); + HANDLE_ATTR(SafeStack); HANDLE_ATTR(NoCapture); HANDLE_ATTR(NoRedZone); HANDLE_ATTR(NoImplicitFloat); diff --git a/lib/Target/X86/X...