similar to: [LLVMdev] Minor API change coming

On 25 June 2011 13:00, Duncan Sands <baldrick at free.fr> wrote: >> 3. Clang/dragonegg need to adapt to the new API (help appreciated!) > > what needs to be done exactly? Background info: http://www.nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt As I understand it, PATypeHolder, OpaqueType and the Module's TypeSymbolTable are gone. Instead, StructTypes can optionally be

Hi List, My IR compiles fine and runs. I've tried to add DebugIR pass so as to be able to debug and profile it (since source is an SQL query all that I can debug and profile is IR itself). When I tried to add it to pass manager I got the following assert: Program received signal SIGABRT, Aborted. 0x00007ffff3fe4425 in __GI_raise (sig=<optimized out>) at

On Jul 12, 2011, at 5:04 AM, Vitaly Lugovskiy wrote: > Hi Chris, > > What's a new way of building recursive types (with C bindings), once > RefineType had been removed? And what's an exact reason for getting > rid of the opaque types - I could not find a relevant discussion in a > mailing list. Hi Vitaly, I didn't add this API, because I'm not very familiar

On Jun 25, 2011, at 11:59 AM, Jay Foad wrote: > On 25 June 2011 13:00, Duncan Sands <baldrick at free.fr> wrote: >>> 3. Clang/dragonegg need to adapt to the new API (help appreciated!) >> >> what needs to be done exactly? > > Background info: http://www.nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt > > As I understand it, PATypeHolder, OpaqueType

> 1. Clang - Jay, do you have a patch for this?  Can you create a branch of the clang repo or send an updated version of the patch to the list? I've created a clang type-system-rewrite branch and committed all my purely mechanical changes: de-constifying llvm::Types as necessary, and using the new llvm::StructType::createNamed/setBody to create the "implicit" structs used by

Hi Chris, > 3. Clang/dragonegg need to adapt to the new API (help appreciated!) what needs to be done exactly? Ciao, Duncan.

hi Duncan, >> >>> That said, it still doesn't compile because you seem >>> to have LLVM from svn installed not llvm-2.9, and dragonegg-2.9 needs to >>> be >> >> yep, the dragonegg is also from svn when i try: /home/ether/local/gcc-4.5/bin/gcc -S -O1 -o - -fplugin=$HOME/sources/dragonegg/dragonegg.so -fplugin-arg-dragonegg-emit-ir

> cc1: error: Cannot load plugin /home/ether/sources/dragonegg/dragonegg.so > /home/ether/sources/dragonegg/dragonegg.so: undefined symbol: > llvm::StructType::get(llvm::LLVMContext&, llvm::ArrayRef<llvm::Type > const*>, bool) PS: You may get this if you built using llvm-svn headers but linked with llvm-2.9 libraries.

Trunk output: > [ 32%] Building CXX object > examples/Kaleidoscope/Chapter3/CMakeFiles/Kaleidoscope-Ch3.dir/toy.cpp.o > /home/mdriftmeyer/DeveloperProjects/LLVMProject/trunk/llvm/tools/clang/utils/TableGen/ClangDiagnosticsEmitter.cpp:158:17: > error: > no member named 'getSuperClassRanges' in 'llvm::Record'; did you > mean 'getSuperClasses'? >

An update on the type-system-rewrite branch (http://llvm.org/viewvc/llvm-project/llvm/branches/type-system-rewrite/): It's now to the point where it passes all regression tests all of single source (and most of externals/multisource) when using an LLVM 2.9 version of clang to compile programs to a rbc file. I have what looks like one more subtle type mapping bug to track down, which will

Hi ether, > i install mpc-0.8.2 in /home/ether/local/, and gcc-4.5 is configure with: > $HOME/sources/gcc-4.5/configure --enable-plugin --enable-lto > --prefix=$HOME/local/gcc-4.5/ --enable-languages=c,c++ > --disable-bootstrap --disable-multilib --with-mpc=$HOME/local > --with-libelf=$HOME/local because GCC headers include mpc.h, when dragonegg uses GCC headers then it needs to

We have the situation where we are trying to send to a server that has a cluster configuration. When we negotiate, it tells us to talk 3.11. When we actually try to send the file, the share's max protocol is actually only 3.02 and so the Microsoft server sends a NT_STATUS_SMB_BAD_CLUSTER_DIALECT, which means they expect the client to reconnect negotiating only 3.02 as max protocol. Looking

On Dec 6, 2006, at 10:44 AM, Andrew Lenharth wrote: > Currently, Structure layout is left to targets, which implement them > according to the ABI of that platform. While this is fine for most > structures, it makes packed structures very ugly. All fields in a > packed type must be converted to byte arrays with casts to access > fields, which bloats accesses and obsfucates the

I'm building a StructType without a body using StructType *StructType::create(LLVMContext &Context, StringRef Name); and then later adding a body to with setBody(). It starts of isOpaque() == true, and isSized() == false, and after I add the body, isOpaque() == false, but isSized() is still false. If I create a StructType using StructType * StructType ::create(LLVMContext

On Thu, 12 Jun 2008 16:05:19 -0400, Gordon Henriksen wrote: > > Partially opaque types can be refined. This section of the programmer's > manual is applicable: > > http://llvm.org/docs/ProgrammersManual.html#BuildRecType > > — Gordon Here it is: : // Create the initial outer struct : PATypeHolder StructTy = OpaqueType::get(); : std::vector<const Type*> Elts; :

Hi Rick, On 22/01/13 09:04, Rick Mann wrote: > I'm building a StructType without a body using > > StructType *StructType::create(LLVMContext &Context, StringRef Name); > > and then later adding a body to with setBody(). It starts of isOpaque() == true, and isSized() == false, and after I add the body, isOpaque() == false, but isSized() is still false. this is the standard

Hey guys, I could use some advice on a special case of a function pointer as a formal argument. I would like the function pointer type to contain the actual signature of the function, i.e. not a pointer to var args function. This becomes an issue when I have a function which can take a pointer to itself as an argument... our terminology for this is "a recursive procedure". That is, of

I've made all the suggested changes - however, I'm having a bit of problem running the tests. I started "make check" and several hours later it had only made it through about 1/3 of the tests. I'm not sure what the deal is. On Mon, Jan 18, 2010 at 1:40 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 16, 2010, at 11:15 AM, Talin wrote: > > OK

Thanks for the response Chris, On Jul 26, 2011, at 0:44, Chris Lattner wrote: > > On Jul 25, 2011, at 10:50 AM, Garrison Venn wrote: > >> Several people on this list have reported issues with the linker regarding a >> named StructType instance with the same name in two different modules >> being resolved into two StructTypes with different names due to StructType::

Hi, how can i correctly calculate the size of a member of a struct (including alignment etc)? This doesn't work : const StructType *STy = cast<StructType>(Ty); for (StructType::element_iterator I = STy->element_begin(), E = STy->element_end(); I != E; ++I) { usigned size =I->get()->getScalarSizeInBits(); //often