From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BB452385ED4B; Fri, 31 May 2024 13:50:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB452385ED4B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1717163418; bh=6zX3gC0K+II64o0NdWUq4kRUsr1CWoY8z8dEooB3SpA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BIk1RDVRaTVPAmVSrbGUttnFTstVGb08+FS8aovTLS9kDwKD1I31AmA0XMFVdh7SA DZabk/s1pqJnZKef004Ksx37kYpC6FeXoDqczNy0+YS9Flmur4F4XSORuC3pRp6O0o y44bqy6uX0b1DvxOUTPyEuic5W7GHUIZ6jo3ovd0= From: "law at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115298] [15 Regression] Various targets failing DSE tests after recent changes Date: Fri, 31 May 2024 13:50:18 +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: 15.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: law at gcc dot gnu.org 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: 15.0 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=3D115298 --- Comment #2 from Jeffrey A. Law --- What still doesn't make sense is why nds32 would be special here. It doesn= 't do anything special with flag_delete_null_pointer_checks and I don't think = it uses any of the address space hooks. So why does nds32 behave differently = than x86?=