From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id DD4083858C52; Mon,  1 Aug 2022 13:35:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD4083858C52
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.4.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: herrtimson at yahoo dot de
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: 
Message-ID: <bug-106466-4-lKPtBPph2r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106466-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106466-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2022 13:35:22 -0000

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

--- Comment #9 from tt_1 <herrtimson at yahoo dot de> ---
started with pr105998=20

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=3Di386 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:=20

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.=
=20

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.=20

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.=