public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "herrtimson at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106466] ICE in In function 'bool jxl_skcms_Parse(const void*, size_t, skcms_ICCProfile*)': at skcms/skcms.cc:1004:6 internal compiler error: Segmentation fault
Date: Mon, 01 Aug 2022 13:35:21 +0000 [thread overview]
Message-ID: <bug-106466-4-lKPtBPph2r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106466-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106466
--- Comment #9 from tt_1 <herrtimson at yahoo dot de> ---
started with pr105998
commit 20bb976fb6a853d4f79577278ac2f01622946b61
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sat, 18 Jun 2022 09:07:13 +0000
varasm: Fix up ICE in narrowing_initializer_constant_valid_p [PR105998]
The following testcase ICEs because there is NON_LVALUE_EXPR (location
wrapper) around a VAR_DECL and has TYPE_MODE V2SImode and
SCALAR_INT_TYPE_MODE on that ICEs. Or for -m32 -march=i386 TYPE_MODE
is DImode, but SCALAR_INT_TYPE_MODE still uses the raw V2SImode and ICEs
too.
2022-06-18 Jakub Jelinek <jakub@redhat.com>
PR middle-end/105998
* varasm.c (narrowing_initializer_constant_valid_p): Check
SCALAR_INT_MODE_P instead of INTEGRAL_MODE_P, also break on
! INTEGRAL_TYPE_P and do the same check also on op{0,1}'s type.
* c-c++-common/pr105998.c: New test.
here is how I did it:
the first bad version is 10.4.0-RC
the last good version is 10-20220616
Its just a handfull of commits between those snapshots, so I compiled
10-20220616 and added those commits subsequentially, via local patch files.
Its a problem though that cross-compiler doesn't confirm the ICE, and native
compile is kind if heisenbugging around. I'll ask the original author if he has
any suggestion what could happen here.
gcc-11.3.0 is not affected, as the fix landed for gcc-11.4.0 and I haven't yet
found the time to test these snapshots.
next prev parent reply other threads:[~2022-08-01 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 15:47 [Bug c++/106466] New: " herrtimson at yahoo dot de
2022-07-28 15:48 ` [Bug c++/106466] " herrtimson at yahoo dot de
2022-07-28 16:19 ` herrtimson at yahoo dot de
2022-07-28 16:25 ` [Bug middle-end/106466] " pinskia at gcc dot gnu.org
2022-07-28 16:30 ` [Bug c++/106466] " herrtimson at yahoo dot de
2022-07-29 7:29 ` rguenth at gcc dot gnu.org
2022-07-29 13:19 ` herrtimson at yahoo dot de
2022-08-01 8:52 ` marxin at gcc dot gnu.org
2022-08-01 8:53 ` marxin at gcc dot gnu.org
2022-08-01 13:35 ` herrtimson at yahoo dot de [this message]
2022-08-02 19:48 ` herrtimson at yahoo dot de
2022-08-02 19:51 ` herrtimson at yahoo dot de
2022-08-02 21:00 ` [Bug middle-end/106466] " herrtimson at yahoo dot de
2022-08-02 21:01 ` herrtimson at yahoo dot de
2022-08-02 21:02 ` pinskia 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-106466-4-lKPtBPph2r@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).