search for: ocamllangimpl7

Displaying 8 results from an estimated 8 matches for "ocamllangimpl7".

2010 Apr 05
3
[LLVMdev] Linking with C Library
>> You need to figure out how to pass -rdynamic to the linker, like I said before. http://llvm.org/docs/tutorial/OCamlLangImpl7.html mentions it, but I don't know enough about the ocaml build process to say whether that'll work. I believe I'm already doing that, properly by passing -ccopt -rdynamic to ocamlopt: ocamlopt -cc g++ -ccopt -rdynamic -linkall $(LIBFILES) -o alpha $(OBJFILES) I've also tried writ...
2014 Oct 19
2
[LLVMdev] SSA for memory objects
Hello, I'm looking to learn more about what is available for memory versioning or inducing some kind of SSA for memory objects. I found this page: http://llvm.org/docs/tutorial/OCamlLangImpl7.html#memory-in-llvm Which says: "[LLVM] does not require (or permit) memory objects to be in SSA form.... In LLVM, instead of encoding dataflow analysis of memory into the LLVM IR, it is handled with Analysis Passes which are computed on demand." However, there is no mention of wh...
2010 Apr 06
0
[LLVMdev] Linking with C Library
On Mon, Apr 5, 2010 at 3:27 PM, Nyx <mcheva at cs.mcgill.ca> wrote: > >>> You need to figure out how to pass -rdynamic to the linker, like I > said before. http://llvm.org/docs/tutorial/OCamlLangImpl7.html > mentions it, but I don't know enough about the ocaml build process to > say whether that'll work. > > I believe I'm already doing that, properly by passing -ccopt -rdynamic to > ocamlopt: > ocamlopt -cc g++ -ccopt -rdynamic -linkall $(LIBFILES) -o alpha $(OBJFIL...
2011 Jan 21
4
[LLVMdev] all LLVM Instructions that may write to memory -- other than StoreInst?
I need to figure out all LLVM Instructions that may write to memory. In http://llvm.org/docs/tutorial/OCamlLangImpl7.html, it mentions that "In LLVM, all memory accesses are explicit with load/store instructions, and it is carefully designed not to have (or need) an "address-of" operator." I take this as "StoreInst is the only one that writes to memory". However, this doesn't...
2010 Apr 05
0
[LLVMdev] Linking with C Library
...mand.org/man_pages/nm1.html says that a 'U' in that column means "The symbol is undefined." (It's there so the dynamic loader knows to pull it out of a .so, I think.) You need to figure out how to pass -rdynamic to the linker, like I said before. http://llvm.org/docs/tutorial/OCamlLangImpl7.html mentions it, but I don't know enough about the ocaml build process to say whether that'll work. > I > tried modifying my code to use fputs instead of puts instead, but had no > success, however, I still get: > > LLVM ERROR: Tried to execute an unknown external function:...
2011 Jan 21
0
[LLVMdev] all LLVM Instructions that may write to memory -- other than StoreInst?
On 1/21/11 2:50 PM, Chuck Zhao wrote: > I need to figure out all LLVM Instructions that may write to memory. > > In http://llvm.org/docs/tutorial/OCamlLangImpl7.html, it mentions that > "In LLVM, all memory accesses are explicit with load/store > instructions, and it is carefully designed not to have (or need) an > "address-of" operator." > > I take this as "StoreInst is the only one that writes to memory". T...
2010 Apr 05
2
[LLVMdev] Linking with C Library
I tried running nm - D | grep "puts" on the binary compiled by the OCaml compiler. It outputs the following: 08161b00 T camlRuntime__rt_fputs_208 08161a20 T camlRuntime__rt_puts_198 U fputs I'm assuming this means that fputs is linked dynamically, and puts is not. I tried modifying my code to use fputs instead of puts instead, but had no success, however, I still get:
2011 Jan 21
1
[LLVMdev] all LLVM Instructions that may write to memory -- other than StoreInst?
...ill NEVER write stack because its doesn't have a result. Thank you Chuck On 1/21/2011 5:33 PM, John Criswell wrote: > On 1/21/11 2:50 PM, Chuck Zhao wrote: >> I need to figure out all LLVM Instructions that may write to memory. >> >> In http://llvm.org/docs/tutorial/OCamlLangImpl7.html, it mentions that >> "In LLVM, all memory accesses are explicit with load/store >> instructions, and it is carefully designed not to have (or need) an >> "address-of" operator." >> >> I take this as "StoreInst is the only one that writes...