* Request update GCC
@ 2017-06-25 2:22 Steven Penny
2017-06-25 4:03 ` JonY
2017-08-10 1:10 ` Steven Penny
0 siblings, 2 replies; 12+ messages in thread
From: Steven Penny @ 2017-06-25 2:22 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-25 2:22 Request update GCC Steven Penny
@ 2017-06-25 4:03 ` JonY
2017-06-26 1:11 ` JonY
2017-06-26 10:16 ` Marco Atzeri
2017-08-10 1:10 ` Steven Penny
1 sibling, 2 replies; 12+ messages in thread
From: JonY @ 2017-06-25 4:03 UTC (permalink / raw)
To: cygwin
[-- 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 --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-25 4:03 ` JonY
@ 2017-06-26 1:11 ` JonY
2017-06-26 19:27 ` Christian Franke
2017-06-26 10:16 ` Marco Atzeri
1 sibling, 1 reply; 12+ messages in thread
From: JonY @ 2017-06-26 1:11 UTC (permalink / raw)
To: cygwin
[-- 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 --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-25 4:03 ` JonY
2017-06-26 1:11 ` JonY
@ 2017-06-26 10:16 ` Marco Atzeri
2017-06-27 1:09 ` JonY
1 sibling, 1 reply; 12+ messages in thread
From: Marco Atzeri @ 2017-06-26 10:16 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-26 10:16 ` Marco Atzeri
@ 2017-06-27 1:09 ` JonY
2017-06-27 11:33 ` Marco Atzeri
0 siblings, 1 reply; 12+ messages in thread
From: JonY @ 2017-06-27 1:09 UTC (permalink / raw)
To: cygwin
[-- 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 --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-27 1:09 ` JonY
@ 2017-06-27 11:33 ` Marco Atzeri
2017-06-28 2:22 ` Ken Brown
0 siblings, 1 reply; 12+ messages in thread
From: Marco Atzeri @ 2017-06-27 11:33 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-27 11:33 ` Marco Atzeri
@ 2017-06-28 2:22 ` Ken Brown
2017-06-28 11:34 ` Marco Atzeri
0 siblings, 1 reply; 12+ messages in thread
From: Ken Brown @ 2017-06-28 2:22 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-06-25 2:22 Request update GCC Steven Penny
2017-06-25 4:03 ` JonY
@ 2017-08-10 1:10 ` Steven Penny
2017-08-13 4:19 ` JonY
1 sibling, 1 reply; 12+ messages in thread
From: Steven Penny @ 2017-08-10 1:10 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Request update GCC
2017-08-10 1:10 ` Steven Penny
@ 2017-08-13 4:19 ` JonY
0 siblings, 0 replies; 12+ messages in thread
From: JonY @ 2017-08-13 4:19 UTC (permalink / raw)
To: cygwin
[-- 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 --]
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-08-13 4:19 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-25 2:22 Request update GCC Steven Penny
2017-06-25 4:03 ` JonY
2017-06-26 1:11 ` JonY
2017-06-26 19:27 ` Christian Franke
2017-06-28 23:14 ` JonY
2017-06-26 10:16 ` Marco Atzeri
2017-06-27 1:09 ` JonY
2017-06-27 11:33 ` Marco Atzeri
2017-06-28 2:22 ` Ken Brown
2017-06-28 11:34 ` Marco Atzeri
2017-08-10 1:10 ` Steven Penny
2017-08-13 4:19 ` JonY
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).