Research with PyPy Translation Toolchain
I am a PhD candidate at the University of Illinois. I am interested in learning more about how to use the PyPy Translation Toolchain as part of a research project. We would like to write some code in Python and generate C code from that. When using the Translation Toolchain, a *.c source file is generated and then compiled with GCC. How do I find where the source files are stored before GCC is called? I want to interface with those *.c files. Adam Smith Ph.D. Candidate University of Illinois at Urbana-Champaign
2012/10/4 Adam R. Smith <smith195@illinois.edu>:
I am a PhD candidate at the University of Illinois. I am interested in learning more about how to use the PyPy Translation Toolchain as part of a research project. We would like to write some code in Python and generate C code from that. When using the Translation Toolchain, a *.c source file is generated and then compiled with GCC. How do I find where the source files are stored before GCC is called? I want to interface with those *.c files. Look at /tmp/<some semirandom directory name>. They're there, nicely named after your modules.
On Thu, Oct 4, 2012 at 8:17 PM, Adam R. Smith <smith195@illinois.edu> wrote:
I am a PhD candidate at the University of Illinois. I am interested in learning more about how to use the PyPy Translation Toolchain as part of a research project. We would like to write some code in Python and generate C code from that. When using the Translation Toolchain, a *.c source file is generated and then compiled with GCC. How do I find where the source files are stored before GCC is called? I want to interface with those *.c files.
Adam Smith Ph.D. Candidate University of Illinois at Urbana-Champaign
Hi Adam Note that PyPy translation toolchain does not compile Python. It compiles RPython, which is a restricted subset of Python. However, we have a Python interpreter written in rPython.
participants (3)
-
Adam R. Smith
-
Alexander Sedov
-
Maciej Fijalkowski