From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request update GCC
Date: Tue, 27 Jun 2017 11:33:00 -0000 [thread overview]
Message-ID: <edeb74a7-60b2-08ce-9c2d-7e5998e1e6f2@gmail.com> (raw)
In-Reply-To: <75758c6e-a76e-02b2-5b72-ac43fa666a20@gmail.com>
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
next prev parent reply other threads:[~2017-06-27 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 2:22 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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=edeb74a7-60b2-08ce-9c2d-7e5998e1e6f2@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).