From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 94C5B3857C5B; Mon, 21 Sep 2020 16:10:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 94C5B3857C5B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1600704631; bh=Z6/qJQSMYhUUXfnoJJ5O9lXv5lVbFmD6n2C/9Tjqb9M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AVu0dAGfT19neS+n8HopnlezOyJCBIJPTZsEnaEH4L7WDcoYZOcNRpGw45brEORLl /hiQQ9Wc/L/FwRajgUzsUZ0MvTwqDocHkfzEvwKQuzOaMeNA5VnqX5KAMT3jo8yEeg OqvDoHC3CSQHyfVI7mvHsM4VO6fCqi3LJf81cK88= From: "simon.willcocks at gmx dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97143] aarch64-none-elf Code generated for array after another array within a global structure marked volatile is broken. Date: Mon, 21 Sep 2020 16:10:31 +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: 8.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.willcocks at gmx dot de X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: resolution bug_status 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2020 16:10:31 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97143 Simon Willcocks changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Simon Willcocks --- Checking the x86 code, as well, I realise that I was wrong, it's not a bug.=