RE: [PATCH v2]middle-end: delay checking for alignment to load [PR118464]

2025-02-13 Thread Tamar Christina
> -Original Message- > From: Richard Sandiford > Sent: Thursday, February 13, 2025 4:55 PM > To: Tamar Christina > Cc: Richard Biener ; gcc-patches@gcc.gnu.org; nd > > Subject: Re: [PATCH v2]middle-end: delay checking for alignment to load > [PR118464] >

Re: [PATCH v2]middle-end: delay checking for alignment to load [PR118464]

2025-02-13 Thread Richard Sandiford
Tamar Christina writes: >> -Original Message- >> That said, I'm quite sure we don't want to have a dr->target_alignment >> that isn't power-of-two, so if the comput doesn't end up with a >> power-of-two value we should leave it as the target prefers and >> fixup (or fail) during vectorizab

RE: [PATCH v2]middle-end: delay checking for alignment to load [PR118464]

2025-02-13 Thread Richard Biener
delay checking for alignment to load > > [PR118464] > > > > > -Original Message- > > > From: Richard Biener > > > Sent: Wednesday, February 12, 2025 2:58 PM > > > To: Tamar Christina > > > Cc: gcc-patches@gcc.gnu.org; nd > > > Subje

RE: [PATCH v2]middle-end: delay checking for alignment to load [PR118464]

2025-02-12 Thread Tamar Christina
> -Original Message- > From: Tamar Christina > Sent: Wednesday, February 12, 2025 3:20 PM > To: Richard Biener > Cc: gcc-patches@gcc.gnu.org; nd > Subject: RE: [PATCH v2]middle-end: delay checking for alignment to load > [PR118464] > > > -Original

RE: [PATCH v2]middle-end: delay checking for alignment to load [PR118464]

2025-02-12 Thread Tamar Christina
> -Original Message- > From: Richard Biener > Sent: Wednesday, February 12, 2025 2:58 PM > To: Tamar Christina > Cc: gcc-patches@gcc.gnu.org; nd > Subject: Re: [PATCH v2]middle-end: delay checking for alignment to load > [PR118464] > > On Tue, 11 Feb

Re: [PATCH v2]middle-end: delay checking for alignment to load [PR118464]

2025-02-12 Thread Richard Biener
On Tue, 11 Feb 2025, Tamar Christina wrote: > Hi All, > > This fixes two PRs on Early break vectorization by delaying the safety checks > to > vectorizable_load when the VF, VMAT and vectype are all known. > > This patch does add two new restrictions: > > 1. On LOAD_LANES targets, where the bu