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 3DD9A3858D38; Tue,  6 Feb 2024 12:47:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3DD9A3858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707223646;
	bh=tlXMte9CSp+0IvaGyhzeYGE0w82MlOnBuFtikhcdIJM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QTYCNzqqPVRDBui3nmXICSXDMefk+rFpbouBADtOoHrMC3yo21+roj8mfJbL4xcRT
	 JK8Xidf44uR94JPlNtI+T4ztM5Ru4Z/TynU4Q+ATwsqzVPDQDTEr+gR28hbC4Phegu
	 GWr8nJ/Yqsgvy0Fgmp0B1QYcGB25gW6MereTYz/c=
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113779] Very inefficient m68k code generated for simple
 copy loop
Date: Tue, 06 Feb 2024 12:47:25 +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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikpelinux at gmail dot com
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-113779-4-oub8AKTtRf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113779-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=3D113779

--- Comment #4 from Mikael Pettersson <mikpelinux at gmail dot com> ---
I'm not sure this is an m68k bug. I tried several targets that have
auto-increment addressing modes (m68k, pdp11, msp430, vax, aarch64) and non=
e of
them would use auto-increment for this test case.=