Request update GCC

Request update GCC

[Steven Penny]

GCC 5.4 was released June 2016, and GCC 6.1 was released April 2016:

http://gcc.gnu.org/releases.html

Here are some key packages:

gcc-core, gcc-g++
==================
- version: 5.4.0-1
- version: 6.3.0-1 [test]
- Jonathan Yong (JonY)

mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-g++
===============================================
- version: 5.4.0-3
- Jonathan Yong (JonY)

mingw64-i686-gcc-core, mingw64-i686-gcc-g++
===========================================
- version: 5.4.0-4
- Jonathan Yong (JonY)

GCC 5 is starting to show its age:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 877 bytes --]

On 06/25/2017 02:21 AM, Steven Penny wrote:
> GCC 5.4 was released June 2016, and GCC 6.1 was released April 2016:
> 
> http://gcc.gnu.org/releases.html
> 
> Here are some key packages:
> 
> gcc-core, gcc-g++
> ==================
> - version: 5.4.0-1
> - version: 6.3.0-1 [test]
> - Jonathan Yong (JonY)
> 
> mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-g++
> ===============================================
> - version: 5.4.0-3
> - Jonathan Yong (JonY)
> 
> mingw64-i686-gcc-core, mingw64-i686-gcc-g++
> ===========================================
> - version: 5.4.0-4
> - Jonathan Yong (JonY)
> 
> GCC 5 is starting to show its age:
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145
> 

Would you mine testing GCC6? IIRC exception handling is broken in 6,
which is why it is stuck in test.

I suppose I can put gcc 6.3 in test soon.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: Request update GCC

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 465 bytes --]

On 06/25/2017 04:03 AM, JonY wrote:
>>
>> GCC 5 is starting to show its age:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145
>>
> 
> Would you mine testing GCC6? IIRC exception handling is broken in 6,
> which is why it is stuck in test.
> 
> I suppose I can put gcc 6.3 in test soon.
> 
> 

Woops, looks like gcc-6.3 is already in test.

Taking a closer look at the bug report, we're still using the old C++
ABI, so we're unaffected.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: Request update GCC

[Christian Franke]

JonY wrote:
> On 06/25/2017 04:03 AM, JonY wrote:
>>> GCC 5 is starting to show its age:
>>>
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145
>>>
>> Would you mine testing GCC6? IIRC exception handling is broken in 6,
>> which is why it is stuck in test.
>>
>> I suppose I can put gcc 6.3 in test soon.
>>
>>
> Woops, looks like gcc-6.3 is already in test.

Its libstdc++6 DLL is broken:
https://cygwin.com/ml/cygwin/2017-02/msg00093.html


Christian


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 764 bytes --]

On 06/26/2017 07:27 PM, Christian Franke wrote:
> JonY wrote:
>> On 06/25/2017 04:03 AM, JonY wrote:
>>>> GCC 5 is starting to show its age:
>>>>
>>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145
>>>>
>>> Would you mine testing GCC6? IIRC exception handling is broken in 6,
>>> which is why it is stuck in test.
>>>
>>> I suppose I can put gcc 6.3 in test soon.
>>>
>>>
>> Woops, looks like gcc-6.3 is already in test.
> 
> Its libstdc++6 DLL is broken:
> https://cygwin.com/ml/cygwin/2017-02/msg00093.html
> 

Good news, I don't see the duplicate addresses anymore after the
binutils update (hopefully I am not reading objdump wrong), however the
slow nm problem which I thought was fixed is still there.

Uploading new gcc soon.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: Request update GCC

[Marco Atzeri]

On 25/06/2017 06:03, JonY wrote:
> On 06/25/2017 02:21 AM, Steven Penny wrote:
>> GCC 5.4 was released June 2016, and GCC 6.1 was released April 2016:
>>
>> http://gcc.gnu.org/releases.html
>>
>> Here are some key packages:
>>
>> gcc-core, gcc-g++
>> ==================
>> - version: 5.4.0-1
>> - version: 6.3.0-1 [test]
>> - Jonathan Yong (JonY)
>>
>>
>
> Would you mine testing GCC6? IIRC exception handling is broken in 6,
> which is why it is stuck in test.
>
> I suppose I can put gcc 6.3 in test soon.
>

Jon,

are you building the compilers on cygwin or cross compiling ?

I was trying to test the patch for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47030
as it is blocking PETSC porting,
but I was unable to build 6.3.0-1 from your
source package.


In file included from 
/cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
x86_64/src/gcc-6.3.0/gcc/rtl.h:31:0,
                  from 
/cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
x86_64/src/gcc-6.3.0/gcc/genopinit.c:25:
/cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g
cc/real.h:36:35: warning: division by zero [-Wdiv-by-zero]
  #define SIGSZ   (SIGNIFICAND_BITS / HOST_BITS_PER_LONG)

/cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g
cc/real.h:49:21: note: in expansion of macro ‘SIGSZ’
    unsigned long sig[SIGSZ];

Regards
Marco



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]

On 06/26/2017 10:16 AM, Marco Atzeri wrote:
> 
> Jon,
> 
> are you building the compilers on cygwin or cross compiling ?
> 
> I was trying to test the patch for
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47030
> as it is blocking PETSC porting,
> but I was unable to build 6.3.0-1 from your
> source package.
> 
> 
> In file included from
> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
> x86_64/src/gcc-6.3.0/gcc/rtl.h:31:0,
>                  from
> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
> x86_64/src/gcc-6.3.0/gcc/genopinit.c:25:
> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g
> 
> cc/real.h:36:35: warning: division by zero [-Wdiv-by-zero]
>  #define SIGSZ   (SIGNIFICAND_BITS / HOST_BITS_PER_LONG)
> 
> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g
> 
> cc/real.h:49:21: note: in expansion of macro ‘SIGSZ’
>    unsigned long sig[SIGSZ];

On Cygwin itself, shouldn't that be 32bit and 64bit respectively for Cygwin?



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: Request update GCC

[Marco Atzeri]

On 27/06/2017 03:08, JonY wrote:
> On 06/26/2017 10:16 AM, Marco Atzeri wrote:
>>
>> Jon,
>>
>> are you building the compilers on cygwin or cross compiling ?
>>
>> I was trying to test the patch for
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47030
>> as it is blocking PETSC porting,
>> but I was unable to build 6.3.0-1 from your
>> source package.
>>
>>
>> In file included from
>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
>> x86_64/src/gcc-6.3.0/gcc/rtl.h:31:0,
>>                  from
>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
>> x86_64/src/gcc-6.3.0/gcc/genopinit.c:25:
>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g
>>
>> cc/real.h:36:35: warning: division by zero [-Wdiv-by-zero]
>>  #define SIGSZ   (SIGNIFICAND_BITS / HOST_BITS_PER_LONG)
>>
>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g
>>
>> cc/real.h:49:21: note: in expansion of macro ‘SIGSZ’
>>    unsigned long sig[SIGSZ];
>
> On Cygwin itself, shouldn't that be 32bit and 64bit respectively for Cygwin?

In theory

gcc/real.h:#define SIGNIFICAND_BITS   (128 + HOST_BITS_PER_LONG)

gcc/hwint.h:#define HOST_BITS_PER_LONG  (CHAR_BIT * SIZEOF_LONG)


but I do not understand why SIGSZ is wrong defined.






--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[Ken Brown]

On 6/27/2017 7:32 AM, Marco Atzeri wrote:
> On 27/06/2017 03:08, JonY wrote:
>> On 06/26/2017 10:16 AM, Marco Atzeri wrote:
>>>
>>> Jon,
>>>
>>> are you building the compilers on cygwin or cross compiling ?
>>>
>>> I was trying to test the patch for
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47030
>>> as it is blocking PETSC porting,
>>> but I was unable to build 6.3.0-1 from your
>>> source package.
>>>
>>>
>>> In file included from
>>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
>>> x86_64/src/gcc-6.3.0/gcc/rtl.h:31:0,
>>>                  from
>>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.
>>> x86_64/src/gcc-6.3.0/gcc/genopinit.c:25:
>>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g 
>>>
>>>
>>> cc/real.h:36:35: warning: division by zero [-Wdiv-by-zero]
>>>  #define SIGSZ   (SIGNIFICAND_BITS / HOST_BITS_PER_LONG)
>>>
>>> /cygdrive/e/cyg_pub/devel/gcc/gcc-6.3.0-1.src/gcc-6.3.0-1.x86_64/src/gcc-6.3.0/g 
>>>
>>>
>>> cc/real.h:49:21: note: in expansion of macro ‘SIGSZ’
>>>    unsigned long sig[SIGSZ];
>>
>> On Cygwin itself, shouldn't that be 32bit and 64bit respectively for 
>> Cygwin?
> 
> In theory
> 
> gcc/real.h:#define SIGNIFICAND_BITS   (128 + HOST_BITS_PER_LONG)
> 
> gcc/hwint.h:#define HOST_BITS_PER_LONG  (CHAR_BIT * SIZEOF_LONG)
> 
> 
> but I do not understand why SIGSZ is wrong defined.

FWIW, I just rebuilt gcc-6.3.0-1 from source on 64-bit Cygwin without 
getting that warning.

Ken



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[Marco Atzeri]

On 28/06/2017 04:22, Ken Brown wrote:
>
> FWIW, I just rebuilt gcc-6.3.0-1 from source on 64-bit Cygwin without
> getting that warning.
>
> Ken
>

Thanks.
It helps to focus on my PC installation

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[Steven Penny]

On Sat, 24 Jun 2017 19:21:57, Steven Penny wrote:
> gcc-core, gcc-g++
> ==================
> - version: 5.4.0-1
> - version: 6.3.0-1 [test]
> - Jonathan Yong (JonY)
> 
> mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-g++
> ===============================================
> - version: 5.4.0-3
> - Jonathan Yong (JonY)
> 
> mingw64-i686-gcc-core, mingw64-i686-gcc-g++
> ===========================================
> - version: 5.4.0-4
> - Jonathan Yong (JonY)

http://cygwin.com/ml/cygwin/2017-06/msg00310.html

Now that the issue with readline has been resolved, thanks to great work by
Corinna and Eric, I wanted to revist some other of my issues. I am reposting
this because it is a new month.

Some work was done on this in June and July, but I still do not see even a test
version with the mingw64-*-gcc-* packages. I use Cygwin quite a bit, but when I
can I prefer to build Windows native versions of programs, this way I can share
them without worrying about the Cygwin DLL.

Can we please release at least test versions of the mingw64-*-gcc-* packages?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Request update GCC

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]

On 08/10/2017 01:10 AM, Steven Penny wrote:
> On Sat, 24 Jun 2017 19:21:57, Steven Penny wrote:
>> gcc-core, gcc-g++
>> ==================
>> - version: 5.4.0-1
>> - version: 6.3.0-1 [test]
>> - Jonathan Yong (JonY)
>>
>> mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-g++
>> ===============================================
>> - version: 5.4.0-3
>> - Jonathan Yong (JonY)
>>
>> mingw64-i686-gcc-core, mingw64-i686-gcc-g++
>> ===========================================
>> - version: 5.4.0-4
>> - Jonathan Yong (JonY)
> 
> http://cygwin.com/ml/cygwin/2017-06/msg00310.html
> 
> Now that the issue with readline has been resolved, thanks to great work by
> Corinna and Eric, I wanted to revist some other of my issues. I am
> reposting
> this because it is a new month.
> 
> Some work was done on this in June and July, but I still do not see even
> a test
> version with the mingw64-*-gcc-* packages. I use Cygwin quite a bit, but
> when I
> can I prefer to build Windows native versions of programs, this way I
> can share
> them without worrying about the Cygwin DLL.
> 
> Can we please release at least test versions of the mingw64-*-gcc-*
> packages?
> 

Sure, I'll start bringing up mingw-w64 6.x within the week.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]