From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B056B3858C01; Fri, 3 Nov 2023 07:50:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B056B3858C01 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698997841; bh=OvalfuFppYdgu+bmcKnQRFojVVV1rmMv5hJVT030yOY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=clo0wpDISzpNp0avujZo9j3qOwo+6CTa2yphBmj2t8g+1uWsa7A29I6yzA0HA8jq3 rbMbql2funkmybhLf/HBOo98mTHlqTLADqo9wkxwg9+e2dLuURqTndp1hjiNSH8OdA bEHo/VCMeCZRBWiENppRm5++WSpcr/1Sqm0I8adA= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112357] Documentation for vect-max-peeling-for-alignment references -1 but -1 does not work Date: Fri, 03 Nov 2023 07:50:41 +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: 14.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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: cf_reconfirmed_on bug_status everconfirmed 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112357 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-11-03 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Richard Biener --- -param=3Dvect-max-peeling-for-alignment=3D Common Joined UInteger Var(param_vect_max_peeling_for_alignment) Init(-1) IntegerRange(0, 64) Param Optimization Maximum number of loop peels to enhance alignment of data references in a l= oop. Interesting that we allow an Init() with an out-of-range value. Possibly a way to detect whether the parameter was specified or not ... Documentation should probably be adjusted to mention when not specified no limit applies (the limit is the vectorization factor - 1)=