Note that that needs to be done when using Clang, too. If you leave the
default GC root finder, you'll get some crazy errors.
On Mon, Feb 17, 2014 at 4:45 PM, Romain Guillebert wrote:
> Hi Kirk
>
> If you want to compile with something that is not gcc, you should use
> "--gcrootfinder=shadowstac
Hi Kirk
If you want to compile with something that is not gcc, you should use
"--gcrootfinder=shadowstack" as a translation time option, otherwise it
uses a gcc specific root finding method (I don't know if it's done
automatically).
Romain
On 02/17, Kirk Liberty wrote:
> Thank you! It's it corre
Thank you! It's it correct to assume that the generated C code will be
identical regardless of the computer PyPy it's translated on? This allowing
for translation on one machine, and compilation on another?
Kirk
On Feb 17, 2014 2:20 PM, "Yury V. Zaytsev" wrote:
> On Mon, 2014-02-17 at 14:15 -050
On Mon, 2014-02-17 at 14:15 -0500, Kirk Liberty wrote:
> Are the C files that are written as one of the last steps of
> translation written in q way that they can be rebuilt many times?
Yes, have a look at the /tmp directory. You can delete the build
artifacts and re-run the edited Makefile witho
Hello all,
I'm looking to do some experiments with different C compilers and flags for
PyPy, but I don't want to have to go through the entire translation process
only to change a flag. Are the C files that are written as one of the last
steps of translation written in q way that they can be rebui
