Re: [PATCH] Make uninit PHI processing more consistent

2022-08-30 Thread Richard Biener via Gcc-patches
get to see the connection of m_best_candidate != NULL meaning m_best_candidate_len being initialized. I've pushed the following with an added testcase and omitting the meanwhile fixed expmed.cc hunk. Richard. >From da1558c957799b4a46ddc2e7496150bf7a9926b5 Mon Sep 17 00:00:00 2001 From: Richard

Re: [PATCH] Make uninit PHI processing more consistent

2022-08-29 Thread Richard Biener via Gcc-patches
On Mon, 29 Aug 2022, Richard Biener wrote: [...] > The patch correctly diagnoses an uninitalized use of 'regnum' > in store_bit_field_1 but also diagnoses an uninitialized use of > best_match::m_best_candidate_len which I've chosen to silence > without analyzing it in detail (I'm doing that right

[PATCH] Make uninit PHI processing more consistent

2022-08-29 Thread Richard Biener via Gcc-patches
Currently the main working of the maybe-uninit pass is to scan over all PHIs with possibly undefined arguments, diagnosing whether there's a direct not guarded use. For not guarded uses in PHIs those are queued for later processing and to make the uninit analysis PHI def handling work, mark the PH