On 3/2/20 11:38 AM, Jeff Law wrote:
On Mon, 2020-03-02 at 11:29 -0500, Marek Polacek wrote:
On Mon, Mar 02, 2020 at 09:25:35AM -0700, Jeff Law wrote:
On Mon, 2020-03-02 at 10:45 -0500, Marek Polacek wrote:
Ping: Jeff, see the question below.  Thanks.
Sorry, totally missed the question.  I'm guessing you want me to run it
through
the Fedora build tester?

Yeah -- we want to allow a more strict narrow checking even in pre-C+20
modes, and we're wondering about the fallout.  So re-compiling Fedora
packages would be useful.
Is the error easy to identify from a diagnostic?  If so that would avoid having
to get fresh baselines.  I can just apply the patch, build gcc, then spin up a
single build of everything.

Not always; sometimes making something ill-formed just changes overload resolution

On further thought, it seems unnecessary to make this change at this point in the release cycle. Let's defer this to GCC 11.

Jason

Reply via email to