On Wed, May 18, 2016 at 12:22 AM, Robert Bradshaw wrote:
> On Fri, May 13, 2016 at 4:26 AM, Erik Bray wrote:
>> On Thu, May 12, 2016 at 12:55 AM, Greg Ewing
>> wrote:
>>> Erik Bray wrote:
A developer who writes some code that
happens to use long double isn't going to think themsel
On Fri, May 13, 2016 at 4:26 AM, Erik Bray wrote:
> On Thu, May 12, 2016 at 12:55 AM, Greg Ewing
> wrote:
>> Erik Bray wrote:
>>>
>>> A developer who writes some code that
>>> happens to use long double isn't going to think themselves "Gosh, I
>>> guess I can't accept `long double` here because i
On Thu, May 12, 2016 at 12:55 AM, Greg Ewing
wrote:
> Erik Bray wrote:
>>
>> A developer who writes some code that
>> happens to use long double isn't going to think themselves "Gosh, I
>> guess I can't accept `long double` here because it may cause Cython to
>> generate code that contains "truncl
Erik Bray wrote:
A developer who writes some code that
happens to use long double isn't going to think themselves "Gosh, I
guess I can't accept `long double` here because it may cause Cython to
generate code that contains "truncl"
Sounds to me like Cython shouldn't be taking it upon
itself to g
On Tue, May 10, 2016 at 8:01 AM, Robert Bradshaw
wrote:
> On Wed, May 4, 2016 at 8:01 AM, Erik Bray wrote:
>> On Tue, May 3, 2016 at 7:15 PM, Robert Bradshaw wrote:
>>> On Tue, May 3, 2016 at 3:04 AM, Erik Bray wrote:
I agree that it would be safest not to use long double where long
d
On Wed, May 4, 2016 at 8:01 AM, Erik Bray wrote:
> On Tue, May 3, 2016 at 7:15 PM, Robert Bradshaw wrote:
>> On Tue, May 3, 2016 at 3:04 AM, Erik Bray wrote:
>>> I agree that it would be safest not to use long double where long
>>> double functions are not support, and an application that does s
On Tue, May 3, 2016 at 7:15 PM, Robert Bradshaw wrote:
> On Tue, May 3, 2016 at 3:04 AM, Erik Bray wrote:
>>
>> On Thu, Apr 28, 2016 at 9:29 AM, Robert Bradshaw
>> wrote:
>> > On Wed, Apr 27, 2016 at 3:07 AM, Erik Bray
>> > wrote:
>> >>
>> >> On Tue, Apr 26, 2016 at 10:55 PM, Robert Bradshaw
>
On Tue, May 3, 2016 at 3:04 AM, Erik Bray wrote:
> On Thu, Apr 28, 2016 at 9:29 AM, Robert Bradshaw
> wrote:
> > On Wed, Apr 27, 2016 at 3:07 AM, Erik Bray
> wrote:
> >>
> >> On Tue, Apr 26, 2016 at 10:55 PM, Robert Bradshaw
> >> wrote:
> >> > On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray
> >> >
On Thu, Apr 28, 2016 at 9:29 AM, Robert Bradshaw
wrote:
> On Wed, Apr 27, 2016 at 3:07 AM, Erik Bray wrote:
>>
>> On Tue, Apr 26, 2016 at 10:55 PM, Robert Bradshaw
>> wrote:
>> > On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray
>> > wrote:
>> >>
>> >> On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
>
On Wed, Apr 27, 2016 at 3:07 AM, Erik Bray wrote:
> On Tue, Apr 26, 2016 at 10:55 PM, Robert Bradshaw
> wrote:
> > On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray
> wrote:
> >>
> >> On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
> >> wrote:
> >> > Hi,
> >> > certainly we did something with Sage on
On Wed, Apr 27, 2016 at 12:07 PM, Erik Bray wrote:
> On Tue, Apr 26, 2016 at 10:55 PM, Robert Bradshaw wrote:
>> On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray wrote:
>>>
>>> On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
>>> wrote:
>>> > Hi,
>>> > certainly we did something with Sage on cygwin to
On Tue, Apr 26, 2016 at 10:55 PM, Robert Bradshaw wrote:
> On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray wrote:
>>
>> On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
>> wrote:
>> > Hi,
>> > certainly we did something with Sage on cygwin to work around these...
>> > Just in case,
>>
>> From what I c
On Tue, Apr 26, 2016 at 2:56 PM Robert Bradshaw wrote:
> On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray wrote:
>
>> On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
>> wrote:
>> > Hi,
>> > certainly we did something with Sage on cygwin to work around these...
>> > Just in case,
>>
>> From what I can
On Tue, Apr 26, 2016 at 8:36 AM, Erik Bray wrote:
> On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
> wrote:
> > Hi,
> > certainly we did something with Sage on cygwin to work around these...
> > Just in case,
>
> From what I can tell there are several places where Sage has hacked
> around this
On 2016-04-26 16:58, Erik Bray wrote:
The problem now is that many of libm long double functions like sqrtl,
tanl, etc. are missing on Cygwin
Just to understand the issue better, can you elaborate how this impacts
Cython?
___
cython-devel mailing li
On Tue, Apr 26, 2016 at 5:16 PM, Dima Pasechnik
wrote:
> Hi,
> certainly we did something with Sage on cygwin to work around these...
> Just in case,
>From what I can tell there are several places where Sage has hacked
around this issue in different packages, but it's not doing anything
specifica
Hi,
certainly we did something with Sage on cygwin to work around these...
Just in case,
Dima
On Tue, Apr 26, 2016 at 3:58 PM, Erik Bray wrote:
> Hi again,
>
> Sorry if I'm spamming the list too much, but I've encountered another
> pretty serious and unfortunate issue with Cython on Cygwin.
>
> T
Hi again,
Sorry if I'm spamming the list too much, but I've encountered another
pretty serious and unfortunate issue with Cython on Cygwin.
The problem now is that many of libm long double functions like sqrtl,
tanl, etc. are missing on Cygwin (missing from newlib to be specific).
I think this is
18 matches
Mail list logo
