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 668E63858C60; Tue, 14 May 2024 09:04:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 668E63858C60
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715677496;
	bh=46R3b67LTuv7Mj7OCpROfLkjnPGZUhDWXJY8SQ/URiI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=M2K3bcwWdWjt6vgM7DBh5jdHSZmJ4DJ6K+7sCBclUviXe3z5e9GsZfWruoNH8Ihjk
	 Jn0eTK1NuJHxIGqTBhnBHCT2NQSN7fu8edECSGefpw9SbcfjSzMfkxSiNXdQxU6Lvt
	 mCBqerrU93iHVL7uD7YpEdHgpzxZ4QTK5bOXs/Pw=
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114995] C++23 Assume keyword not being used
 for vectorization
Date: Tue, 14 May 2024 09:04:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 15.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: aldyh at gcc dot gnu.org
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: attachments.created
Message-ID: <bug-114995-4-UK9tDqORiE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114995-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=3D114995

--- Comment #10 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Created attachment 58202
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D58202&action=3Dedit
proof of concept implementing a range-op entry for builtin_assume_aligned

Something like this (properly coded and enhanced) would work.

The pointers_handled_p() cruft is temporary boilerplate to indicate that we
only support a fold-range() of PRANGE =3D IRANGE op PRANGE for this operati=
on.=20
This is going away when the dust settles.=