Displaying 6 results from an estimated 6 matches for "link_onc".
Did you mean:
linkonc
2009 Dec 27
2
[LLVMdev] ocaml bindings
...8c05e69647e import/llvm.org/llvm/bindings/ocaml/llvm/llvm.ml
--- a/import/llvm.org/llvm/bindings/ocaml/llvm/llvm.ml Fri Dec 25 17: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
+ | Alwaysinli...
2009 Dec 28
0
[LLVMdev] ocaml bindings
.../llvm/bindings/ocaml/llvm/llvm.ml
> --- a/import/llvm.org/llvm/bindings/ocaml/llvm/llvm.ml Fri Dec 25 17: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...
2016 Feb 23
2
RFC: Add guard intrinsics to LLVM
On Mon, Feb 22, 2016 at 11:18 PM, Chandler Carruth <chandlerc at gmail.com> wrote:
>> # step A: Introduce an `interposable` function attribute
>>
>> We can bike shed on the name and the exact specification, but the
>> general idea is that you cannot do IPA / IPO over callsites calling
>> `interposable` functions without inlining them. This attribute will
2016 Feb 23
2
RFC: Add guard intrinsics to LLVM
...nkage type, and
>> can add our restriction to the available_externally linkage.
>
>
> Interesting example, I agree it seems quite broken. Even more interesting, I
> can't see anything we do in LLVM that prevents this from breaking
> essentially everywhere. =[[[[[[
>
> link_once and link_once_odr at least seem equally broken because we don't
> put the caller and callee into a single comdat or anything to ensure that
> the optimized one is selected at link time.
>
> But there are also multiple different kinds of overriding we should think
> about:
>
&...
2007 Nov 27
0
[LLVMdev] Fibonacci example in OCaml
...sibility"). So types would be `i32
rather than i32_type and int_predicate and real_predicate would become
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
> >...
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