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 6713A3858C56; Thu,  4 Apr 2024 17:45:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6713A3858C56
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712252715;
	bh=qT2CKnDX68VRKGn2uS1G5vyxhYqlYD3UFuDD6mKoQ60=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Kq464nCN0YbiaC9XNvFgULWohpfsH/bpZT+73NycbeCirwEANEr3pagKhnVYirhNW
	 Gp7HbK+wZ1E6CBXbgNhVLNehVt7P2FMYKo7FUuO9XyWXDzOrOWZqYsilruyOKV8ZCB
	 AyGZzF2Q6mZgIQRpLyKqoANK2xPfgaI7GJ8WGDsE=
From: "sainan+gcc.bugzilla at calamity dot gg" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110773] [Aarch64] crash (SIGBUS) due to atomic
 instructions on under-aligned memory
Date: Thu, 04 Apr 2024 17:45:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sainan+gcc.bugzilla at calamity dot gg
X-Bugzilla-Status: UNCONFIRMED
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-110773-4-ce4ElEemmr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110773-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #7 from Sainan <sainan+gcc.bugzilla at calamity dot gg> ---
(In reply to Wilco from comment #6)
> That does not make any sense. The only thing I think might happen is that
> your structure is not correctly aligned (for example by using a custom
> memory allocator). Can you check the address of count when it fails? (sho=
uld
> be in the crash logs, or you can see it in gdb or just printf it).

I feel silly for not thinking of printing the address, but now that I did, I
see the final hexit is '9' and so it just so happens this CPU can't deal wi=
th
that...=