public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "philipp.classen at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66982] New: Internal compiler error: Segmentation fault in C++14 code (followup of #65973)
Date: Thu, 23 Jul 2015 21:30:00 -0000	[thread overview]
Message-ID: <bug-66982-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 66982
           Summary: Internal compiler error: Segmentation fault in C++14
                    code (followup of #65973)
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: philipp.classen at gmx dot net
  Target Milestone: ---

Created attachment 36045
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36045&action=edit
gzipped output of "-freport-bug"

Bug #65973 solved one C++14 internal compiler error. That is good news, but my
program still crashes when compiling it with gcc 5.2.0:

g++ -freport-bug -DHAVE_CONFIG_H -I.  -Wall -Wfatal-errors -Wextra
-Wno-type-limits -Wstrict-aliasing -Wvla -Wdisabled-optimization
-Wdouble-promotion  -pipe  --std=c++14 -D
EXTENDED_PARALLEL_LOGGING__DEPENDS_ON_TARGET__  -DUSE_TABLEBASES
-DUSE_NALIMOV_TABLEBASES    -DUSE_BITBASES -DUSE_SINGLE_PAWN_BITBASES
-DUSE_TWO_PAWNS_BITBASES -DUSE_RAMMED_PAWNS_BITBASES     -g3
-DAVOID_EXPENSIVE_DEBUG_OPTIONS   -I gmock-bundle/include -I
gmock-bundle/gtest/include -g  -MT fastdebug-bitbases.o -MD -MP -MF
.deps/fastdebug-bitbases.Tpo -c -o fastdebug-bitbases.o `test -f 'bitbases.cpp'
|| echo './'`bitbases.cpp

In file included from bitbases.cpp:6:0:
constants.h:247:10:   in constexpr expansion of ‘SQ_MASK(0)’
constants.h:248:55: internal compiler error: Segmentation fault
   SQ_MASK(A5) | SQ_MASK(A6) | SQ_MASK(A7) | SQ_MASK(A8);

Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
Preprocessed source stored into /tmp/ccpYk9IH.out file, please attach this to
your bugreport.
>From gcc-bugs-return-493151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jul 23 21:39:52 2015
Return-Path: <gcc-bugs-return-493151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73797 invoked by alias); 23 Jul 2015 21:39:52 -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 73754 invoked by uid 48); 23 Jul 2015 21:39:48 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66981] [graphite] delinearization of arrays
Date: Thu, 23 Jul 2015 21:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: spop at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66981-4-ezCc1YImWS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66981-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-07/txt/msg02041.txt.bz2
Content-length: 154

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

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this related to PR61000?


                 reply	other threads:[~2015-07-23 21:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-66982-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).