public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bplummer at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67680] New: Seg Fault in gcc 4.9.3 compiling libiberty/floatformat.c when building gcc 5.2.1 on Cygwin 64 on Windows
Date: Tue, 22 Sep 2015 16:22:00 -0000	[thread overview]
Message-ID: <bug-67680-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67680

            Bug ID: 67680
           Summary: Seg Fault in gcc 4.9.3 compiling
                    libiberty/floatformat.c when building gcc 5.2.1 on
                    Cygwin 64 on Windows
           Product: gcc
           Version: 4.9.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bplummer at hotmail dot com
  Target Milestone: ---

both the configure and the make args were default.  I've tried a wide variety
of args for both configure and make and the error is blindingly consistent.

Here are the details :

Brian@MBPWin7-64 ~/gnu/gcc/gcc-5.2.0/build/libiberty
$ gmake
if [ x"" != x ]; then \
  gcc -c -DHAVE_CONFIG_H -g  -I. -I../../libiberty/../include  -W -Wall
-Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic  
../../libiberty/floatformat.c -o pic/floatformat.o; \
else true; fi
if [ x"" != x ]; then \
  gcc -c -DHAVE_CONFIG_H -g  -I. -I../../libiberty/../include  -W -Wall
-Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic   
../../libiberty/floatformat.c -o noasan/floatformat.o; \
else true; fi
gcc -c -DHAVE_CONFIG_H -g  -I. -I../../libiberty/../include  -W -Wall
-Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic 
../../libiberty/floatformat.c -o floatformat.o
../../libiberty/floatformat.c: In function ‘floatformat_to_double’:
../../libiberty/floatformat.c:529:2: internal compiler error: Segmentation
fault
  dto = ldexp (1.0, exponent);
  ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Makefile:773: recipe for target 'floatformat.o' failed
gmake: *** [floatformat.o] Error 1

Brian@MBPWin7-64 ~/gnu/gcc/gcc-5.2.0/build/libiberty
$ uname -a
CYGWIN_NT-6.1 MBPWin7-64 2.2.1(0.289/5/3) 2015-08-20 11:42 x86_64 Cygwin

Brian@MBPWin7-64 ~/gnu/gcc/gcc-5.2.0/build/libiberty
$ gcc --version
gcc (GCC) 4.9.3
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>From gcc-bugs-return-497817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 22 16:24:24 2015
Return-Path: <gcc-bugs-return-497817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72330 invoked by alias); 22 Sep 2015 16:24:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72272 invoked by uid 48); 22 Sep 2015 16:24:16 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67680] Seg Fault in gcc 4.9.3 compiling libiberty/floatformat.c when building gcc 5.2.1 on Cygwin 64 on Windows
Date: Tue, 22 Sep 2015 16:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-67680-4-9c2vlNIZu6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67680-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67680-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01795.txt.bz2
Content-length: 594

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg680

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-09-22
                 CC|                            |mpolacek at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Can you provide the preprocessed source?


             reply	other threads:[~2015-09-22 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 16:22 bplummer at hotmail dot com [this message]
2015-09-23  5:38 ` [Bug c/67680] " bplummer at hotmail dot com
2015-09-23  5:43 ` bplummer at hotmail dot com
2015-09-24  6:53 ` mpolacek at gcc dot gnu.org
2015-09-24 15:17 ` bplummer at hotmail dot com
2015-09-25 14:13 ` mpolacek at gcc dot gnu.org

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=bug-67680-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).