Displaying 7 results from an estimated 7 matches for "llvmvoidtypekind".
2012 May 07
4
[LLVMdev] Discussion of eliminating the void type
...I am willing to do "eliminating the void type" project. Is there anyone
working on it?
=== Overview ===
The general concept is to replaced void with {}. And 'ret void' is a
synonym of 'ret {} {}.'
=== Further Implementation Details ===
1. Deleting VoidTyID
2. Deleting LLVMVoidTypeKind (one-to-one relation between VoidTyID and
LLVMVoidTypeKind)
3. Use StructTy* VoidTy instead of Type VoidTy
VoidTy may be Identified struct. In addition to error occurs at
test/Analysis/BasicAA/empty.ll
because of using literal struct "{}" as VoidTy
4. Re-implement isVoidTy()....
2012 May 07
0
[LLVMdev] Discussion of eliminating the void type
...(clang, dragonegg) need to produce
something instead of void, and {} is an example of what they might produce, but
they should not be obliged to use that. For example they could use [] or {{}}
etc.
> === Further Implementation Details ===
>
> 1. Deleting VoidTyID
Yes!
> 2. Deleting LLVMVoidTypeKind (one-to-one relation between VoidTyID and
> LLVMVoidTypeKind)
Yes!
> 3. Use StructTy* VoidTy instead of Type VoidTy
No! This doesn't make any sense to me. Why would having a definition for
VoidTy be needed or desirable?
> VoidTy may be Identified struct. In addition to error...
2007 Sep 17
1
[LLVMdev] C interface
Hi Gordon,
> > I'm authoring a C interface to the LLVM IR type system.
It's great to see a C interface being added. A minor niggle:
> +typedef enum {
> + LLVMVoidTypeKind = 0, /* type with no size */
> ...
> +typedef enum {
> + LLVMExternalLinkage = 0,/* Externally visible function */
> ...
> +typedef enum {
> + LLVMDefaultVisibility = 0, /* The GV is visible */
It's defined by the language that the first enumerate's zero so the
init...
2012 May 07
1
[LLVMdev] Discussion of eliminating the void type
...mething instead of void, and {} is an example of what they might produce, but
> they should not be obliged to use that. For example they could use [] or {{}}
> etc.
>
>> === Further Implementation Details ===
>>
>> 1. Deleting VoidTyID
> Yes!
>
>> 2. Deleting LLVMVoidTypeKind (one-to-one relation between VoidTyID and
>> LLVMVoidTypeKind)
> Yes!
>
>> 3. Use StructTy* VoidTy instead of Type VoidTy
> No! This doesn't make any sense to me. Why would having a definition for
> VoidTy be needed or desirable?
>
>> VoidTy may be Ident...
2007 Sep 17
0
[LLVMdev] C interface
On Sep 12, 2007, at 01:01, Gordon Henriksen wrote:
> I'm authoring a C interface to the LLVM IR type system. Since this
> is Really Quite Tedious, I would like to solicit opinions before I
> get too far down any paths that seem offensive. I've attached the
> header, where I've mapped a portion of Module and most of Type and
> its subclasses. This is working, and
2013 Sep 30
1
[LLVMdev] RFC: llvm-shlib-test (Was: [llvm] r191029 - llvm-c: Make LLVMGetFirstTarget a proper prototype)
Attached is what I got thus far.
What I'm struggling with is proper integration in build system. What
is in there is just wild guesses from my side, both on autoconf and
cmake variants. It would be great if someone with proper knowledge of
the buildsystems could have a look. Also I'm not sure how to properly
handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is
2007 Sep 12
7
[LLVMdev] C interface
Hi all,
I'm authoring a C interface to the LLVM IR type system. Since this is
Really Quite Tedious, I would like to solicit opinions before I get
too far down any paths that seem offensive. I've attached the header,
where I've mapped a portion of Module and most of Type and its
subclasses. This is working, and I've built ocaml bindings on top of
it.[1] My intent is to