From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 6F547385803F; Fri, 10 Dec 2021 17:48:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6F547385803F
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/28680] i686 builds broken with -ftree-vectorize
Date: Fri, 10 Dec 2021 17:48:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: build
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: siddhesh at sourceware dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28680-131-VLKAXE0CwQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28680-131@http.sourceware.org/bugzilla/>
References: <bug-28680-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2021 17:48:31 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D28680

--- Comment #2 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
I don't know, it seems quite like a glibc issue to me.

The configure check to see if ebp is usable with the current flags is
simplistic compared to actual usage and any enhancement of that check would=
 be
flaky since it relies on knowledge of when the compiler needs ebp for the f=
rame
pointer.  The ebp based inlining is a hack and may not make sense in the lo=
ng
term but I don't know if i686 will exist in that time frame :)

I can confirm that disabling the vectorizer with gcc12 works FWIW, but I th=
ink
dropping the asm("ebp") hack is a better idea.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=