Displaying 4 results from an estimated 4 matches for "external_weak".
Did you mean:
extern_weak
2009 Dec 27
2
[LLVMdev] ocaml bindings
...:35:09 2009 -0800
+++ b/import/llvm.org/llvm/bindings/ocaml/llvm/llvm.ml Sun Dec 27 11:38:15 2009 -0800
@@ -42,13 +42,18 @@
| External
| Available_externally
| Link_once
+ | Link_once_odr
| Weak
+ | Weak_odr
| Appending
| Internal
+ | Private
| Dllimport
| Dllexport
| External_weak
| Ghost
+ | Common
+ | Linker_private
end
module Visibility = struct
@@ -79,6 +84,15 @@
| Nest
| Readnone
| Readonly
+ | Noinline
+ | Alwaysinline
+ | Optforsize
+ | Stackprotect
+ | Stackprotectreq
+ | Nocapture
+ | Noredzone
+ | Noimplicitfloat
+ | Naked
end
module...
2009 Dec 28
0
[LLVMdev] ocaml bindings
...aml/llvm/llvm.ml Sun Dec 27 11:38:15 2009 -0800
> @@ -42,13 +42,18 @@
> | External
> | Available_externally
> | Link_once
> + | Link_once_odr
> | Weak
> + | Weak_odr
> | Appending
> | Internal
> + | Private
> | Dllimport
> | Dllexport
> | External_weak
> | Ghost
> + | Common
> + | Linker_private
> end
>
> module Visibility = struct
> @@ -79,6 +84,15 @@
> | Nest
> | Readnone
> | Readonly
> + | Noinline
> + | Alwaysinline
> + | Optforsize
> + | Stackprotect
> + | Stackprotectreq
> + |...
2007 Nov 27
0
[LLVMdev] Fibonacci example in OCaml
...ome
overlapping sum types, e.g. `ugt is valid for both. I'd also rather see
structuring than identifier bloat, e.g.:
module Linkage = struct
type linkage =
[ `External
| `Link_once
| `Weak
| `Appending
| `Internal
| `Dllimport
| `Dllexport
| `External_weak
| `Ghost ]
external linkage : llvalue -> linkage = "llvm_linkage"
end
> > I'd rather box everything rather than tag ints to start with. I'll
> > relegate that to a potential optimization.
>
> You could go about it that way, sure. Memory pressure will...
2007 Nov 26
4
[LLVMdev] Fibonacci example in OCaml
On Nov 26, 2007, at 14:18, Jon Harrop wrote:
> On Monday 26 November 2007 16:21, Gordon Henriksen wrote:
>>
>
>> Unfortunately, even if the bindings were more strongly typed, it
>> would still be structurally possible to build invalid LLVM code, so
>> you've just got to take care not to violate the invariants, then
>> use the verifier as a