From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3D9153858D32; Mon, 9 Oct 2023 16:22:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3D9153858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1696868579; bh=91X9NhA9cdiB5h9pZNXf4Y6kiKpfeDMXDdrZk9izp/g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ATbZW5VmsXdBj8xXUdyI/UhR84thjoMiYHSDCnJEEMcP8OowAeSo64i45Je4aq6PW xYKmd5d1ir4pidas0HdEMSmeJ/RkXKwp6WmPpB2EGwMcxD5Ntbje9bn+mGSlrBQy7z 3ZHtuVzjSGCnIE5QBbzNNnyLMjle/4UaOD3ahcnw= From: "tglozar at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111425] ia64: ICE in net/ipv4/fib_semantics.c:1621:1: internal compiler error: Segmentation fault Date: Mon, 09 Oct 2023 16:22:57 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.2.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: tglozar at gmail dot com X-Bugzilla-Status: NEW 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: In-Reply-To: References: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111425 --- Comment #8 from Tom=C3=A1=C5=A1 Glozar --- It looks like somehow a value RTX with rt_cselib set to NULL gets into the hashmap: (gdb) f 1 #1 rtx_equal_for_cselib_1 (x=3D0x2674608, y=3D0x26747f8, memmode=3Dmemmode@entry=3DE_VOIDmode, depth=3Ddepth@entry=3D1) at ../../gcc/cselib.cc:963 963 cselib_val *e =3D canonical_cselib_val (CSELIB_VAL_PTR (x)); (gdb) p debug_rtx(x) (value:DI Program received signal SIGSEGV, Segmentation fault. 0x0000000000a92f96 in rtx_writer::print_rtx_operand_code_0 (this=3D0x7fffffff64c0, in_rtx=3D0x2674608, idx=3D0) at ../../gcc/print-rtl.cc:318 318 fprintf (m_outfile, " %u:%u", val->uid, val->hash); Going one level up: (gdb) p debug_rtx(y) (subreg:SI (value/u:DI 264:376 @0x26747f8/0x2666068) 0) $1 =3D void (gdb) p debug_rtx(x) (subreg:SI (value:DI Program received signal SIGSEGV, Segmentation fault. Not sure how this is related to 5fc4d3e1837, as I understand it, it should = only affect single-bit values, here it is a DI value. I am not familiar with the algorithm, so proceeding further in finding the cause it hard for me. Perhaps someone who knows the algorithm has an idea why that field is NULL.=