[Cython] Fix integer width constant names in stdint.pxd

Hello,

Attached is a quick fix for some typos in stdint.pxd.

Tested with Cython version 0.15.1.

Mansour

Hello,

Attached is a quick fix for some typos in stdint.pxd.

Tested with Cython version 0.15.1.

Mansour

Re: [Cython] Fix integer width constant names in stdint.pxd

Thanks.

On Mon, Jan 2, 2012 at 4:31 PM, Mansour Moufid
<mansourmoufid@...> wrote:
> Hello,
>
> Attached is a quick fix for some typos in stdint.pxd.
>
> Tested with Cython version 0.15.1.
>
> Mansour
>
> _______________________________________________
> cython-devel mailing list
> cython-devel@...
> http://mail.python.org/mailman/listinfo/cython-devel
>

Re: [Cython] Fix integer width constant names in stdint.pxd

Now my issue is as follows.

(I CCed the cython-users list if this question is more appropriate there.)

I have a simple file, int.pyx:

from libc.stdint cimport *
print long(UINT8_MAX)
print long(UINT16_MAX)
print long(UINT32_MAX)
print long(UINT64_MAX)

with the usual setup.py stuff. Compiling and running:

$ python setup.py build_ext --inplace
...
int.c:566:3: warning: overflow in implicit constant conversion [-Woverflow]
...
$ python -c 'import int'
255
65535
-1
-1

So obviously there are overflows here. Checking int.c, I see:

  /* "int.pyx":2
 * from libc.stdint cimport *
 * print long(UINT8_MAX)             # <<<<<<<<<<<<<<
 * print long(UINT16_MAX)

Re: [Cython] Fix integer width constant names in stdint.pxd

On 2 January 2012 22:37, Mansour Moufid <mansourmoufid <at> gmail.com> wrote:
> Now my issue is as follows.
>
> (I CCed the cython-users list if this question is more appropriate there.)
>
> I have a simple file, int.pyx:
>
> from libc.stdint cimport *
> print long(UINT8_MAX)
> print long(UINT16_MAX)
> print long(UINT32_MAX)
> print long(UINT64_MAX)
>
> with the usual setup.py stuff. Compiling and running:
>
> $ python setup.py build_ext --inplace
> ...
> int.c:566:3: warning: overflow in implicit constant conversion [-Woverflow]
> ...
> $ python -c 'import int'
> 255
> 65535
> -1
> -1
>
> So obviously there are overflows here. Checking int.c, I see:
>
>  /* "int.pyx":2
>  * from libc.stdint cimport *
>  * print long(UINT8_MAX)             # <<<<<<<<<<<<<<

Re: [Cython] Fix integer width constant names in stdint.pxd

On Mon, Jan 2, 2012 at 8:48 PM, Lisandro Dalcin <dalcinl <at> gmail.com> wrote:
> On 2 January 2012 22:37, Mansour Moufid <mansourmoufid <at> gmail.com> wrote:
>> Now my issue is as follows.
>>
>> (I CCed the cython-users list if this question is more appropriate there.)
>>
>> I have a simple file, int.pyx:
>>
>> from libc.stdint cimport *
>> print long(UINT8_MAX)
>> print long(UINT16_MAX)
>> print long(UINT32_MAX)
>> print long(UINT64_MAX)
>>
>> with the usual setup.py stuff. Compiling and running:
>>
>> $ python setup.py build_ext --inplace
>> ...
>> int.c:566:3: warning: overflow in implicit constant conversion [-Woverflow]
>> ...
>> $ python -c 'import int'
>> 255
>> 65535
>> -1
>> -1
>>
>> So obviously there are overflows here. Checking int.c, I see:
>>
>>  /* "int.pyx":2
>>  * from libc.stdint cimport *

Re: [Cython] Fix integer width constant names in stdint.pxd

On Mon, Jan 2, 2012 at 5:48 PM, Lisandro Dalcin <dalcinl <at> gmail.com> wrote:
> On 2 January 2012 22:37, Mansour Moufid <mansourmoufid <at> gmail.com> wrote:
>> Now my issue is as follows.
>>
>> (I CCed the cython-users list if this question is more appropriate there.)
>>
>> I have a simple file, int.pyx:
>>
>> from libc.stdint cimport *
>> print long(UINT8_MAX)
>> print long(UINT16_MAX)
>> print long(UINT32_MAX)
>> print long(UINT64_MAX)
>>
>> with the usual setup.py stuff. Compiling and running:
>>
>> $ python setup.py build_ext --inplace
>> ...
>> int.c:566:3: warning: overflow in implicit constant conversion [-Woverflow]
>> ...
>> $ python -c 'import int'
>> 255
>> 65535
>> -1
>> -1
>>
>> So obviously there are overflows here. Checking int.c, I see:
>>
>>  /* "int.pyx":2
>>  * from libc.stdint cimport *

Re: [Cython] Fix integer width constant names in stdint.pxd

Robert Bradshaw, 03.01.2012 03:00:
> On Mon, Jan 2, 2012 at 5:48 PM, Lisandro Dalcin wrote:
>> On 2 January 2012 22:37, Mansour Moufid wrote:
>>> Now my issue is as follows.
>>>
>>> (I CCed the cython-users list if this question is more appropriate there.)
>>>
>>> I have a simple file, int.pyx:
>>>
>>> from libc.stdint cimport *
>>> print long(UINT8_MAX)
>>> print long(UINT16_MAX)
>>> print long(UINT32_MAX)
>>> print long(UINT64_MAX)
>>>
>>> with the usual setup.py stuff. Compiling and running:
>>>
>>> $ python setup.py build_ext --inplace
>>> ...
>>> int.c:566:3: warning: overflow in implicit constant conversion [-Woverflow]
>>> ...
>>> $ python -c 'import int'
>>> 255
>>> 65535
>>> -1
>>> -1
>>>
>>> So obviously there are overflows here. Checking int.c, I see:
>>>
>>>   /* "int.pyx":2

Re: [Cython] Fix integer width constant names in stdint.pxd

On 2 January 2012 23:00, Robert Bradshaw <robertwb <at> math.washington.edu> wrote:
> On Mon, Jan 2, 2012 at 5:48 PM, Lisandro Dalcin <dalcinl <at> gmail.com> wrote:
>> On 2 January 2012 22:37, Mansour Moufid <mansourmoufid <at> gmail.com> wrote:
>>> Now my issue is as follows.
>>>
>>> (I CCed the cython-users list if this question is more appropriate there.)
>>>
>>> I have a simple file, int.pyx:
>>>
>>> from libc.stdint cimport *
>>> print long(UINT8_MAX)
>>> print long(UINT16_MAX)
>>> print long(UINT32_MAX)
>>> print long(UINT64_MAX)
>>>
>>> with the usual setup.py stuff. Compiling and running:
>>>
>>> $ python setup.py build_ext --inplace
>>> ...
>>> int.c:566:3: warning: overflow in implicit constant conversion [-Woverflow]
>>> ...
>>> $ python -c 'import int'
>>> 255
>>> 65535
>>> -1
>>> -1
>>>
>>> So obviously there are overflows here. Checking int.c, I see:
>>>
>>>  /* "int.pyx":2

[Cython] sage-tests failures

I've recently merged my def-node-refactoring branch and found some
bugs, thanks to sage-build.

Then I've found that sage-tests has >100 failures.
So I'm wondering does anybody know what's wrong with sage-tests?

--

-- 
vitja.

Re: [Cython] sage-tests failures

On Sat, Jan 14, 2012 at 6:19 AM, Vitja Makarov
<vitja.makarov@...> wrote:
> I've recently merged my def-node-refactoring branch and found some
> bugs, thanks to sage-build.
>
> Then I've found that sage-tests has >100 failures.
> So I'm wondering does anybody know what's wrong with sage-tests?

Yeah, sage-tests is a great stress-tester for Cython. There were a
couple of spurious failures before, but nothing this bad.

I blame https://github.com/cython/cython/commit/bce8b981a3e71378a164e8c9acca5f00bbbe32d7
which is causing variables to be undefined. Arguably, this is a bug in
Sage, but it was a backwards incompatible change.

- Robert