Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-24 Thread Corinna Vinschen
On Jun 23 17:05, cyg Simple wrote: > On 6/22/2016 1:17 PM, Corinna Vinschen wrote: > > On Jun 22 10:01, Warren Young wrote: > >> Still, you could get similar problems. ifdefs for portable > >> sized-integer types are a particularly rich source of bugs, especially > >> ones where #ifdef WINDOWS pr

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-23 Thread cyg Simple
On 6/22/2016 1:17 PM, Corinna Vinschen wrote: > On Jun 22 10:01, Warren Young wrote: >> Still, you could get similar problems. ifdefs for portable >> sized-integer types are a particularly rich source of bugs, especially >> ones where #ifdef WINDOWS precedes any test that could match Cygwin, >> s

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-22 Thread Corinna Vinschen
On Jun 22 10:01, Warren Young wrote: > On Jun 22, 2016, at 9:36 AM, Corinna Vinschen > wrote: > > > >> 64-bit Windows is LLP64, while 64-bit Linux is LP64 on the same hardware. > > > > s/Linux/Linux and Cygwin/ > > Well, that was unexpected. The FAQ entry is just as old as the first 64 bit re

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-22 Thread Warren Young
On Jun 22, 2016, at 9:36 AM, Corinna Vinschen wrote: > >> 64-bit Windows is LLP64, while 64-bit Linux is LP64 on the same hardware. > > s/Linux/Linux and Cygwin/ Well, that was unexpected. Still, you could get similar problems. ifdefs for portable sized-integer types are a particularly rich

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-22 Thread Corinna Vinschen
On Jun 22 09:29, Warren Young wrote: > On Jun 22, 2016, at 6:39 AM, Marco Atzeri wrote: > > > > > > may be is a piping problem, but there is no evidence; it could be a lot of > > different issues due to 64bit porting. > > I will not be surprise if there is wrong assumption on data size. > > Th

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-22 Thread Warren Young
On Jun 22, 2016, at 6:39 AM, Marco Atzeri wrote: > > > may be is a piping problem, but there is no evidence; it could be a lot of > different issues due to 64bit porting. > I will not be surprise if there is wrong assumption on data size. That’s my guess, too. 64-bit Windows is LLP64, while 6

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-22 Thread Marco Atzeri
On 22/06/2016 03:32, lloyd.w...@yahoo.co.uk wrote: I've reproduced this SaVi-can't-talk-with-Geomview-on-64-bit-cygwin problem on multiple installs How, exactly? Give me the step-by-step. Step by step instructions to build Geomview and SaVi are on: http://sat-net.com/L.Wood/software/SaVi

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-21 Thread lloyd.wood
>>I've reproduced this SaVi-can't-talk-with-Geomview-on-64-bit-cygwin problem >>on multiple installs > How, exactly? Give me the step-by-step. Step by step instructions to build Geomview and SaVi are on: http://sat-net.com/L.Wood/software/SaVi/building-under-Windows/ launch with geomview -r

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-21 Thread Warren Young
On Jun 21, 2016, at 4:54 PM, wrote: > > Three years ago, 64-bit OpenGL not yet working at all was simply motivation > to see how the then-new 64-bit Geomview fleshed out. Why mention OpenGL at all, then? This is part of reducing the problem to a simple test case: remove confounding complexi

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-21 Thread lloyd.wood
Warren, this piping problem on 64-bit Cygwin between Geomview and its modules (of which SaVi is the most used example) is entirely unrelated to OpenGL, and exists when Geomview is compiled without OpenGL. Three years ago, 64-bit OpenGL not yet working at all was simply motivation to see how th

Re: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-21 Thread Warren Young
On Jun 20, 2016, at 10:53 PM, lloyd.w...@yahoo.co.uk wrote: > > Yes, it's the same piping problem of three years ago. …where you were asked to provide a simple test case for the problem, instead of “compile admittedly difficult-to-build package Geomview and use it against one of the most compli

Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-20 Thread lloyd.wood
m 32-bit Cygwin, btw.) - Original Message - From: Jon Turney To: cygwin@cygwin.com Cc: lloyd.w...@yahoo.co.uk Sent: Monday, 20 June 2016, 22:58 Subject: Re: [ANNOUNCEMENT] llvm 3.7.1-2 On 10/06/2016 02:18, lloyd.w...@yahoo.co.uk wrote: > Thanks, picking up 3.7.1-2 from the mirrors.kernel.

Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-20 Thread Jon Turney
On 10/06/2016 02:18, lloyd.w...@yahoo.co.uk wrote: Thanks, picking up 3.7.1-2 from the mirrors.kernel.org site (as it's not mirrored everywhere yet) resolved the 32-bit OpenGL crashing issues with SaVi and Geomview that I reported in May; texturemapping is back. You're welcome. (I've no idea

Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-09 Thread Yaakov Selkowitz
On 6/9/2016 8:18 PM, lloyd.w...@yahoo.co.uk wrote: Thanks, picking up 3.7.1-2 from the mirrors.kernel.org site (as it's not mirrored everywhere yet) resolved the 32-bit OpenGL crashing issues with SaVi and Geomview that I reported in May; texturemapping is back. Glad to hear it. (I've no idea

Re: [ANNOUNCEMENT] llvm 3.7.1-2

2016-06-09 Thread lloyd.wood
Thanks, picking up 3.7.1-2 from the mirrors.kernel.org site (as it's not mirrored everywhere yet) resolved the 32-bit OpenGL crashing issues with SaVi and Geomview that I reported in May; texturemapping is back. (I've no idea how 64-bit OpenGL is doing, as unique Cygwin piping issues there prev

[ANNOUNCEMENT] llvm 3.7.1-2

2016-06-09 Thread Yaakov Selkowitz
The following packages have been uploaded to the Cygwin distribution: * llvm-3.7.1-2 * llvm-doc-3.7.1-2 * libllvm3.7-3.7.1-2 * libllvm-devel-3.7.1-2 The LLVM Core libraries provide a modern source- and target-independent optimizer, along with code generation support for many popular CPUs (as we