[pypy-dev] PyPy Intermediate C Files

[Ryan Gonzalez]

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 <romain.py at gmail.com>wrote:

> 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 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" <yury at shurup.com> wrote:
> >
> > > 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 without re-translating PyPy.
> > >
> > > --
> > > Sincerely yours,
> > > Yury V. Zaytsev
> > >
> > >
> > >
>
> > _______________________________________________
> > pypy-dev mailing list
> > pypy-dev at python.org
> > https://mail.python.org/mailman/listinfo/pypy-dev
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>



-- 
Ryan
If anybody ever asks me why I prefer C++ to C, my answer will be simple:
"It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was
nul-terminated."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20140217/eb1257cc/attachment.html>