This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Tom.Browder, amaury.forgeotdarc, barry, pitrou, skrah, vstinner
Date 2011-01-12.13:32:07
SpamBayes Score 0.00029439683
Marked as misclassified No
Message-id <1294839123.3718.15.camel@localhost.localdomain>
In-reply-to <1294837716.55.0.23707415042.issue9880@psf.upfronthosting.co.za>
Content
[...]
> 
> gcc-4.6 -O1 -ftree-vectorize
> -------------------------------------
> 0x0000000000480991 <+5041>:  mov    %eax,%ecx
> 0x0000000000480993 <+5043>:  sub    %edx,%ecx
> 0x0000000000480995 <+5045>:  mov    %ecx,(%r12,%rax,4)
> 0x0000000000480999 <+5049>:  movzbl 0x0(%rbp,%rax,1),%ecx
> 0x000000000048099e <+5054>:  lea    0x1(%rdx),%esi
> 0x00000000004809a1 <+5057>:  cmp    $0x9,%cl
> 0x00000000004809a4 <+5060>:  cmovne %edx,%esi
> 0x00000000004809a7 <+5063>:  cmove  %esi,%edx
> 0x00000000004809aa <+5066>:  setne  %cl
> 0x00000000004809ad <+5069>:  movzbl %cl,%ecx
> 0x00000000004809b0 <+5072>:  lea    0x1(%rax,%rcx,2),%rax
> 0x00000000004809b5 <+5077>:  cmp    %rax,%rdi
> 0x00000000004809b8 <+5080>:  jg     0x480991 <PyCode_Optimize+5041>
> -------------------------------------

Looks like code generation is borked.
(it lacks a compare to 0x59 or 0x5a (90), and "setne" wouldn't be the
right instruction anyway)
History
Date User Action Args
2011-01-12 13:32:09pitrousetrecipients: + pitrou, barry, amaury.forgeotdarc, vstinner, skrah, Tom.Browder
2011-01-12 13:32:07pitroulinkissue9880 messages
2011-01-12 13:32:07pitroucreate