From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0B633385803B; Mon, 7 Dec 2020 14:08:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0B633385803B From: "hubicka at ucw dot cz" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98172] Update -mtune=generic for the current Intel and AMD processors Date: Mon, 07 Dec 2020 14:08:38 +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: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at ucw dot cz 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: 11.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 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, 07 Dec 2020 14:08:39 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98172 --- Comment #4 from Jan Hubicka --- > > What kind of updates you propose? >=20 > For one thing, memcpy/memset should be expanded to REP MOVSB/STOSB, never > MOVSL/MOVSQ. For core cost tables we use: /* core_cost should produce code tuned for Core familly of CPUs. */=20=20= =20=20=20=20=20=20=20=20=20=20 static stringop_algs core_memcpy[2] =3D {=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 {libcall, {{1024, rep_prefix_4_byte, true}, {-1, libcall, false}}},=20=20= =20=20=20=20=20=20=20=20=20 {libcall, {{24, loop, true}, {128, rep_prefix_8_byte, true},=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 {-1, libcall, false}}}};=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 static stringop_algs core_memset[2] =3D {=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 {libcall, {{6, loop_1_byte, true},=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 {24, loop, true},=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 {8192, rep_prefix_4_byte, true},=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 {-1, libcall, false}}},=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 {libcall, {{24, loop, true}, {512, rep_prefix_8_byte, true},=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 {-1, libcall, false}}}};=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 So we use mosl/modsw for blocks up to 8k in some cases. What is output of contrib/bench-stringop on later cores? Honza >=20 > --=20 > You are receiving this mail because: > You are on the CC list for the bug.=