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 B1BFB3857B80; Tue, 28 Nov 2023 10:32:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B1BFB3857B80
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701167573;
	bh=rsnbX5rREJmMaOzBOXgzVPMm3cwaFMM/mygz7TTPvow=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=h5z8cWw535TdPFit+57DbcjtA3bJTl3/K/YseoWD0TzxG/qwHgT7ZRQw4ocKe62Hy
	 JtxRgrIXlfAh7LspH4Fn04arwAmrdfhCWs8sZkKvRjhoV436Q+4Gf4IK5c2pIIfCWD
	 PX2Qa8WWfBisdObnA3t6VLdBhBBFB2GeRxUbdPGc=
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109849] suboptimal code for vector walking loop
Date: Tue, 28 Nov 2023 10:32:51 +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: 13.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109849-4-MoOCT0MPnp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109849-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=3D109849

--- Comment #27 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #26)
> (In reply to GCC Commits from comment #23)
> > https://gcc.gnu.org/g:aae723d360ca26cd9fd0b039fb0a616bd0eae363
> >=20
> > commit r14-5831-gaae723d360ca26cd9fd0b039fb0a616bd0eae363
> > Author: Martin Jambor <mjambor@suse.cz>
> > Date:   Fri Nov 24 17:32:35 2023 +0100
> >=20
> >     sra: SRA of non-escaped aggregates passed by reference to calls
> >=20=20=20=20=20
>=20
> I'm seeing a large number of libstdc++ testsuite failures, bisected to th=
is
> patch.
>=20
> For example:
>=20
> make check -C x86_64-pc-linux-gnu/libstdc++-v3
> RUNTESTFLAGS=3D"conformance.exp=3D21_strings/basic_string/operators/char/=
1.cc
> --target_board=3Dunix/-D_GLIBCXX_USE_CXX11_ABI=3D0"
>=20

Unfortunately I cannot reproduce this, the above (on pristine master
commit 006e90e1344 on an x86_64-linux) results in:

Running target unix/-D_GLIBCXX_USE_CXX11_ABI=3D0
Running
/home/mjambor/gcc/small/src/libstdc++-v3/testsuite/libstdc++-dg/conformance=
.exp
...
PASS: 21_strings/basic_string/operators/char/1.cc  -std=3Dgnu++17 (test for
excess errors)
PASS: 21_strings/basic_string/operators/char/1.cc  -std=3Dgnu++17 execution=
 test

Can you please try if
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638318.html
fixes this?=