public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mike at cchtml dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96391] New: internal compiler error: in linemap_compare_locations, at libcpp/line-map.c:1359
Date: Thu, 30 Jul 2020 15:51:07 +0000 [thread overview]
Message-ID: <bug-96391-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96391
Bug ID: 96391
Summary: internal compiler error: in linemap_compare_locations,
at libcpp/line-map.c:1359
Product: gcc
Version: 10.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mike at cchtml dot com
Target Milestone: ---
Compiling the Wine Gecko project on Fedora for a Windows target produces an
internal compiler error. GCC 10.1 and 10.2 are affected. Last known working
with GCC 9.2.1.
When I compile it with the default arguments I get the error.
When I compile it with '-save-temps' to get the preprocessed file no error
occurs. No error occurs if I compile the preprocessed file either.
I'm not sure what to provide to reproduce this besides the SRPM file to compile
it.
https://kojipkgs.fedoraproject.org//packages/mingw-wine-gecko/2.47.1/2.fc32/src/mingw-wine-gecko-2.47.1-2.fc32.src.rpm
next reply other threads:[~2020-07-30 15:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 15:51 mike at cchtml dot com [this message]
2020-07-30 15:52 ` [Bug c++/96391] " mike at cchtml dot com
2020-07-31 6:15 ` [Bug preprocessor/96391] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-07-31 6:18 ` marxin at gcc dot gnu.org
2020-07-31 18:13 ` mike at cchtml dot com
2020-09-04 17:50 ` jan.smets at nokia dot com
2020-10-07 19:46 ` qinzhao at gcc dot gnu.org
2020-10-09 16:48 ` qinzhao at gcc dot gnu.org
2020-10-09 16:49 ` qinzhao at gcc dot gnu.org
2020-12-06 3:18 ` mike at cchtml dot com
2021-02-09 0:10 ` dmalcolm at gcc dot gnu.org
2021-02-09 7:06 ` jan.smets at nokia dot com
2021-02-09 14:40 ` dmalcolm at gcc dot gnu.org
2021-02-10 0:04 ` mike at cchtml dot com
2021-02-10 11:42 ` dmalcolm at gcc dot gnu.org
2021-02-10 12:15 ` dmalcolm at gcc dot gnu.org
2021-02-10 15:05 ` dmalcolm at gcc dot gnu.org
2021-02-10 15:57 ` rguenther at suse dot de
2021-02-10 16:08 ` qinzhao at gcc dot gnu.org
2021-02-10 16:57 ` dmalcolm at gcc dot gnu.org
2021-02-10 16:58 ` dmalcolm at gcc dot gnu.org
2021-02-10 19:33 ` [Bug preprocessor/96391] [10/11 Regression] ICE in linemap_compare_locations on "CONST VOID" in large C++ files cvs-commit at gcc dot gnu.org
2021-02-10 19:38 ` [Bug preprocessor/96391] [10 " dmalcolm at gcc dot gnu.org
2021-02-10 20:24 ` dmalcolm at gcc dot gnu.org
2021-02-10 23:32 ` qinzhao at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-06-16 15:41 ` cvs-commit at gcc dot gnu.org
2021-06-16 18:33 ` cvs-commit at gcc dot gnu.org
2022-01-25 20:05 ` mike at cchtml dot com
2022-01-26 7:05 ` rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07 8:59 ` rguenth 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-96391-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).