[Python-ideas] WSAPoll and tulip
Guido van Rossum
guido at python.org
Tue Nov 27 18:17:57 CET 2012
Nevertheless the optimizer does crazy things to ceval.c. Trent, can you
confirm you were debugging unoptimized code?
--Guido van Rossum (sent from Android phone)
On Nov 27, 2012 8:57 AM, "Christian Heimes" <christian at python.org> wrote:
> Am 27.11.2012 15:30, schrieb Nick Coghlan:
> > I'm not sure that has anything to do with "yield from", but rather to do
> > with the use of computed gotos
> > (http://hg.python.org/cpython/file/default/Python/ceval.c#l821). For
> > sane stepping in the eval loop, you probably want to build with
> > "--without-computed-gotos" enabled (that's a configure option on Linux,
> > I have no idea how to turn it off on Windows). Even without that, the
> > manual opcode prediction macros are still a bit wacky (albeit easier to
> > follow than the compiler level trickery).
> I don't think the problem is related to computed gotos. Visual Studio
> doesn't support labels as values and therefore doesn't do computed
> gotos, too. It's a special feature of GCC and some other compilers.
> No computed gotos on Windows ;)
> Python-ideas mailing list
> Python-ideas at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas