Message ID | e825d821-73a8-5e5a-4557-51429854def0@linux.ibm.com |
---|---|
State | New |
Headers |
Return-Path: <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C87C4385843C for <patchwork@sourceware.org>; Fri, 17 Sep 2021 09:44:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C87C4385843C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1631871899; bh=lMyxXxfEsQ4Lc7QaK31Xb5rPGpCJESz4eQWDq51MX8U=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:Cc:From; b=kbFb1k3z0Ui92IcRBCdIag5ON7/EU9MCz1pv4z6n89WRsA7XiKC8hr8nKsPvI/Cl0 8JiyE8KoIF3w9iSZ92XEfhqeBVhXywk4lw0Ar8zUdXAq7JuuR4itoMr+KyxBCM1BqG r6zy4Mn/tzncY/sGZ47rmUscu0FvGWxt7almaP1g= X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from mx0b-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by sourceware.org (Postfix) with ESMTPS id 8F74F3858438 for <gcc-patches@gcc.gnu.org>; Fri, 17 Sep 2021 09:43:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8F74F3858438 Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 18H8K0aT011918; Fri, 17 Sep 2021 05:43:04 -0400 Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com with ESMTP id 3b4jqyqxn5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Sep 2021 05:43:04 -0400 Received: from m0098421.ppops.net (m0098421.ppops.net [127.0.0.1]) by pps.reinject (8.16.0.43/8.16.0.43) with SMTP id 18H9ZKvE006931; Fri, 17 Sep 2021 05:43:03 -0400 Received: from ppma06ams.nl.ibm.com (66.31.33a9.ip4.static.sl-reverse.com [169.51.49.102]) by mx0a-001b2d01.pphosted.com with ESMTP id 3b4jqyqxmp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Sep 2021 05:43:03 -0400 Received: from pps.filterd (ppma06ams.nl.ibm.com [127.0.0.1]) by ppma06ams.nl.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 18H9aWG2026386; Fri, 17 Sep 2021 09:43:02 GMT Received: from b06cxnps3075.portsmouth.uk.ibm.com (d06relay10.portsmouth.uk.ibm.com [9.149.109.195]) by ppma06ams.nl.ibm.com with ESMTP id 3b0kqkmrgc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Sep 2021 09:43:02 +0000 Received: from d06av26.portsmouth.uk.ibm.com (d06av26.portsmouth.uk.ibm.com [9.149.105.62]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 18H9gxj744368190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 17 Sep 2021 09:42:59 GMT Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 75B78AE059; Fri, 17 Sep 2021 09:42:59 +0000 (GMT) Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 729F6AE057; Fri, 17 Sep 2021 09:42:57 +0000 (GMT) Received: from kewenlins-mbp.cn.ibm.com (unknown [9.200.147.34]) by d06av26.portsmouth.uk.ibm.com (Postfix) with ESMTP; Fri, 17 Sep 2021 09:42:57 +0000 (GMT) To: GCC Patches <gcc-patches@gcc.gnu.org> Subject: [PATCH] ipa-fnsummary: Remove inconsistent bp_pack_value Message-ID: <e825d821-73a8-5e5a-4557-51429854def0@linux.ibm.com> Date: Fri, 17 Sep 2021 17:42:55 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 Content-Type: text/plain; charset=gbk Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: 2h0nOmYkGhHVFHvQ5OcpHJmci9ty4ulZ X-Proofpoint-GUID: qGw48B0iL9UjR7kW1gAcHy1N-ymzO6Zh X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.182.1,Aquarius:18.0.790,Hydra:6.0.391,FMLib:17.0.607.475 definitions=2021-09-17_04,2021-09-16_01,2020-04-07_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=0 clxscore=1015 priorityscore=1501 suspectscore=0 mlxlogscore=753 malwarescore=0 adultscore=0 mlxscore=0 phishscore=0 impostorscore=0 spamscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2109030001 definitions=main-2109170061 X-Spam-Status: No, score=-11.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_EF, GIT_PATCH_0, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org> List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe> List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/> List-Post: <mailto:gcc-patches@gcc.gnu.org> List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help> List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe> From: "Kewen.Lin via Gcc-patches" <gcc-patches@gcc.gnu.org> Reply-To: "Kewen.Lin" <linkw@linux.ibm.com> Cc: Segher Boessenkool <segher@kernel.crashing.org>, Bill Schmidt <wschmidt@linux.ibm.com>, Jan Hubicka <hubicka@ucw.cz> Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org Sender: "Gcc-patches" <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> |
Series |
ipa-fnsummary: Remove inconsistent bp_pack_value
|
|
Commit Message
Kewen.Lin
Sept. 17, 2021, 9:42 a.m. UTC
Hi, When changing target_info with bitfield, I happened to find this inconsistent streaming in and out. We have the streaming in: bp_pack_value (&bp, info->inlinable, 1); bp_pack_value (&bp, false, 1); bp_pack_value (&bp, info->fp_expressions, 1); while the streaming out: info->inlinable = bp_unpack_value (&bp, 1); info->fp_expressions = bp_unpack_value (&bp, 1) The cleanup of Cilk Plus support seemed to miss to remove the bit streaming out but change with streaming false. By hacking fp_expression_p to return true always, I can see it reads the wrong fp_expressions value (false) out in wpa dumping. Bootstrapped and regress-tested on powerpc64le-linux-gnu Power9. Is it ok for trunk? BR, Kewen ----- gcc/ChangeLog: * ipa-fnsummary.c (ipa_fn_summary_write): Remove inconsistent bitfield streaming out.
Comments
On Fri, Sep 17, 2021 at 11:43 AM Kewen.Lin <linkw@linux.ibm.com> wrote: > > Hi, > > When changing target_info with bitfield, I happened to find this > inconsistent streaming in and out. We have the streaming in: > > bp_pack_value (&bp, info->inlinable, 1); > bp_pack_value (&bp, false, 1); > bp_pack_value (&bp, info->fp_expressions, 1); > > while the streaming out: > > info->inlinable = bp_unpack_value (&bp, 1); > info->fp_expressions = bp_unpack_value (&bp, 1) > > The cleanup of Cilk Plus support seemed to miss to remove the bit > streaming out but change with streaming false. > > By hacking fp_expression_p to return true always, I can see it > reads the wrong fp_expressions value (false) out in wpa dumping. > > Bootstrapped and regress-tested on powerpc64le-linux-gnu Power9. > > Is it ok for trunk? OK for trunk and all affected branches (note we need to bump the LTO minor version there). The issue comes from the removal of cilk+ in r8-4956 which removed the bp_unpack but replaced the bp_pack ... It's a correctness issue as we'll read fp_expressions as always 'false' Thanks, Richard. > > BR, > Kewen > ----- > gcc/ChangeLog: > > * ipa-fnsummary.c (ipa_fn_summary_write): Remove inconsistent > bitfield streaming out. > > diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c > index 2470937460f..31199919405 100644 > --- a/gcc/ipa-fnsummary.c > +++ b/gcc/ipa-fnsummary.c > @@ -4652,7 +4652,6 @@ ipa_fn_summary_write (void) > info->time.stream_out (ob); > bp = bitpack_create (ob->main_stream); > bp_pack_value (&bp, info->inlinable, 1); > - bp_pack_value (&bp, false, 1); > bp_pack_value (&bp, info->fp_expressions, 1); > streamer_write_bitpack (&bp); > streamer_write_uhwi (ob, vec_safe_length (info->conds));
On Fri, Sep 17, 2021 at 12:03 PM Richard Biener <richard.guenther@gmail.com> wrote: > > On Fri, Sep 17, 2021 at 11:43 AM Kewen.Lin <linkw@linux.ibm.com> wrote: > > > > Hi, > > > > When changing target_info with bitfield, I happened to find this > > inconsistent streaming in and out. We have the streaming in: > > > > bp_pack_value (&bp, info->inlinable, 1); > > bp_pack_value (&bp, false, 1); > > bp_pack_value (&bp, info->fp_expressions, 1); > > > > while the streaming out: > > > > info->inlinable = bp_unpack_value (&bp, 1); > > info->fp_expressions = bp_unpack_value (&bp, 1) > > > > The cleanup of Cilk Plus support seemed to miss to remove the bit > > streaming out but change with streaming false. > > > > By hacking fp_expression_p to return true always, I can see it > > reads the wrong fp_expressions value (false) out in wpa dumping. > > > > Bootstrapped and regress-tested on powerpc64le-linux-gnu Power9. > > > > Is it ok for trunk? > > OK for trunk and all affected branches (note we need to bump the > LTO minor version there). The issue comes from the removal > of cilk+ in r8-4956 which removed the bp_unpack but replaced > the bp_pack ... > > It's a correctness issue as we'll read fp_expressions as always 'false' Btw, on branches we could also simply unpack a dummy bit to avoid changing the format. > Thanks, > Richard. > > > > > BR, > > Kewen > > ----- > > gcc/ChangeLog: > > > > * ipa-fnsummary.c (ipa_fn_summary_write): Remove inconsistent > > bitfield streaming out. > > > > diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c > > index 2470937460f..31199919405 100644 > > --- a/gcc/ipa-fnsummary.c > > +++ b/gcc/ipa-fnsummary.c > > @@ -4652,7 +4652,6 @@ ipa_fn_summary_write (void) > > info->time.stream_out (ob); > > bp = bitpack_create (ob->main_stream); > > bp_pack_value (&bp, info->inlinable, 1); > > - bp_pack_value (&bp, false, 1); > > bp_pack_value (&bp, info->fp_expressions, 1); > > streamer_write_bitpack (&bp); > > streamer_write_uhwi (ob, vec_safe_length (info->conds));
Hi Richi, Thanks for the review! on 2021/9/17 下午6:04, Richard Biener wrote: > On Fri, Sep 17, 2021 at 12:03 PM Richard Biener > <richard.guenther@gmail.com> wrote: >> >> On Fri, Sep 17, 2021 at 11:43 AM Kewen.Lin <linkw@linux.ibm.com> wrote: >>> >>> Hi, >>> >>> When changing target_info with bitfield, I happened to find this >>> inconsistent streaming in and out. We have the streaming in: >>> >>> bp_pack_value (&bp, info->inlinable, 1); >>> bp_pack_value (&bp, false, 1); >>> bp_pack_value (&bp, info->fp_expressions, 1); >>> >>> while the streaming out: >>> >>> info->inlinable = bp_unpack_value (&bp, 1); >>> info->fp_expressions = bp_unpack_value (&bp, 1) >>> >>> The cleanup of Cilk Plus support seemed to miss to remove the bit >>> streaming out but change with streaming false. >>> >>> By hacking fp_expression_p to return true always, I can see it >>> reads the wrong fp_expressions value (false) out in wpa dumping. >>> >>> Bootstrapped and regress-tested on powerpc64le-linux-gnu Power9. >>> >>> Is it ok for trunk? >> >> OK for trunk and all affected branches (note we need to bump the >> LTO minor version there). The issue comes from the removal >> of cilk+ in r8-4956 which removed the bp_unpack but replaced >> the bp_pack ... >> >> It's a correctness issue as we'll read fp_expressions as always 'false' > > Btw, on branches we could also simply unpack a dummy bit to avoid > changing the format. > Committed in r12-3721. Thanks! As suggested, the patch for branches is listed below. Is ok for branches 9, 10 and 11 after some trunk burn in time? BR, Kewen ----- gcc/ChangeLog: * ipa-fnsummary.c (inline_read_section): Unpack a dummy bit to keep consistent with the side of streaming out. --- diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c index 18bbae145b9..bf635c1f78a 100644 --- a/gcc/ipa-fnsummary.c +++ b/gcc/ipa-fnsummary.c @@ -4403,13 +4403,20 @@ inline_read_section (struct lto_file_decl_data *file_data, const char *data, bp = streamer_read_bitpack (&ib); if (info) { - info->inlinable = bp_unpack_value (&bp, 1); - info->fp_expressions = bp_unpack_value (&bp, 1); + info->inlinable = bp_unpack_value (&bp, 1); + /* On the side of streaming out, there is still one bit + streamed out between inlinable and fp_expressions bits, + which was used for cilk+ before but now always false. + To remove the bit packing need to bump LTO minor version, + so unpack a dummy bit here to keep consistent instead. */ + bp_unpack_value (&bp, 1); + info->fp_expressions = bp_unpack_value (&bp, 1); } else { - bp_unpack_value (&bp, 1); - bp_unpack_value (&bp, 1); + bp_unpack_value (&bp, 1); + bp_unpack_value (&bp, 1); + bp_unpack_value (&bp, 1); } count2 = streamer_read_uhwi (&ib);
On Tue, Sep 21, 2021 at 4:09 AM Kewen.Lin <linkw@linux.ibm.com> wrote: > > Hi Richi, > > Thanks for the review! > > on 2021/9/17 下午6:04, Richard Biener wrote: > > On Fri, Sep 17, 2021 at 12:03 PM Richard Biener > > <richard.guenther@gmail.com> wrote: > >> > >> On Fri, Sep 17, 2021 at 11:43 AM Kewen.Lin <linkw@linux.ibm.com> wrote: > >>> > >>> Hi, > >>> > >>> When changing target_info with bitfield, I happened to find this > >>> inconsistent streaming in and out. We have the streaming in: > >>> > >>> bp_pack_value (&bp, info->inlinable, 1); > >>> bp_pack_value (&bp, false, 1); > >>> bp_pack_value (&bp, info->fp_expressions, 1); > >>> > >>> while the streaming out: > >>> > >>> info->inlinable = bp_unpack_value (&bp, 1); > >>> info->fp_expressions = bp_unpack_value (&bp, 1) > >>> > >>> The cleanup of Cilk Plus support seemed to miss to remove the bit > >>> streaming out but change with streaming false. > >>> > >>> By hacking fp_expression_p to return true always, I can see it > >>> reads the wrong fp_expressions value (false) out in wpa dumping. > >>> > >>> Bootstrapped and regress-tested on powerpc64le-linux-gnu Power9. > >>> > >>> Is it ok for trunk? > >> > >> OK for trunk and all affected branches (note we need to bump the > >> LTO minor version there). The issue comes from the removal > >> of cilk+ in r8-4956 which removed the bp_unpack but replaced > >> the bp_pack ... > >> > >> It's a correctness issue as we'll read fp_expressions as always 'false' > > > > Btw, on branches we could also simply unpack a dummy bit to avoid > > changing the format. > > > > Committed in r12-3721. Thanks! > > As suggested, the patch for branches is listed below. > > Is ok for branches 9, 10 and 11 after some trunk burn in time? It's OK for branches without waiting, maybe you can do a LTO bootstrap on the branches for extra safety (just in case we're triggering some hidden issues due to the fix). Thanks, Richard. > BR, > Kewen > ----- > gcc/ChangeLog: > > * ipa-fnsummary.c (inline_read_section): Unpack a dummy bit > to keep consistent with the side of streaming out. > > --- > diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c > index 18bbae145b9..bf635c1f78a 100644 > --- a/gcc/ipa-fnsummary.c > +++ b/gcc/ipa-fnsummary.c > @@ -4403,13 +4403,20 @@ inline_read_section (struct lto_file_decl_data *file_data, const char *data, > bp = streamer_read_bitpack (&ib); > if (info) > { > - info->inlinable = bp_unpack_value (&bp, 1); > - info->fp_expressions = bp_unpack_value (&bp, 1); > + info->inlinable = bp_unpack_value (&bp, 1); > + /* On the side of streaming out, there is still one bit > + streamed out between inlinable and fp_expressions bits, > + which was used for cilk+ before but now always false. > + To remove the bit packing need to bump LTO minor version, > + so unpack a dummy bit here to keep consistent instead. */ > + bp_unpack_value (&bp, 1); > + info->fp_expressions = bp_unpack_value (&bp, 1); > } > else > { > - bp_unpack_value (&bp, 1); > - bp_unpack_value (&bp, 1); > + bp_unpack_value (&bp, 1); > + bp_unpack_value (&bp, 1); > + bp_unpack_value (&bp, 1); > } > > count2 = streamer_read_uhwi (&ib); >
on 2021/9/21 下午2:16, Richard Biener wrote: > On Tue, Sep 21, 2021 at 4:09 AM Kewen.Lin <linkw@linux.ibm.com> wrote: >> >> Hi Richi, >> >> Thanks for the review! >> >> on 2021/9/17 下午6:04, Richard Biener wrote: >>> On Fri, Sep 17, 2021 at 12:03 PM Richard Biener >>> <richard.guenther@gmail.com> wrote: >>>> >>>> On Fri, Sep 17, 2021 at 11:43 AM Kewen.Lin <linkw@linux.ibm.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> When changing target_info with bitfield, I happened to find this >>>>> inconsistent streaming in and out. We have the streaming in: >>>>> >>>>> bp_pack_value (&bp, info->inlinable, 1); >>>>> bp_pack_value (&bp, false, 1); >>>>> bp_pack_value (&bp, info->fp_expressions, 1); >>>>> >>>>> while the streaming out: >>>>> >>>>> info->inlinable = bp_unpack_value (&bp, 1); >>>>> info->fp_expressions = bp_unpack_value (&bp, 1) >>>>> >>>>> The cleanup of Cilk Plus support seemed to miss to remove the bit >>>>> streaming out but change with streaming false. >>>>> >>>>> By hacking fp_expression_p to return true always, I can see it >>>>> reads the wrong fp_expressions value (false) out in wpa dumping. >>>>> >>>>> Bootstrapped and regress-tested on powerpc64le-linux-gnu Power9. >>>>> >>>>> Is it ok for trunk? >>>> >>>> OK for trunk and all affected branches (note we need to bump the >>>> LTO minor version there). The issue comes from the removal >>>> of cilk+ in r8-4956 which removed the bp_unpack but replaced >>>> the bp_pack ... >>>> >>>> It's a correctness issue as we'll read fp_expressions as always 'false' >>> >>> Btw, on branches we could also simply unpack a dummy bit to avoid >>> changing the format. >>> >> >> Committed in r12-3721. Thanks! >> >> As suggested, the patch for branches is listed below. >> >> Is ok for branches 9, 10 and 11 after some trunk burn in time? > > It's OK for branches without waiting, maybe you can do a LTO bootstrap > on the branches for extra safety (just in case we're triggering some hidden > issues due to the fix). Thanks! LTO bootstrapped on the branches, separately committed via r11-9024, r10-10146 and r9-9740. BR, Kewen > > Thanks, > Richard. > >> BR, >> Kewen >> ----- >> gcc/ChangeLog: >> >> * ipa-fnsummary.c (inline_read_section): Unpack a dummy bit >> to keep consistent with the side of streaming out. >> >> --- >> diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c >> index 18bbae145b9..bf635c1f78a 100644 >> --- a/gcc/ipa-fnsummary.c >> +++ b/gcc/ipa-fnsummary.c >> @@ -4403,13 +4403,20 @@ inline_read_section (struct lto_file_decl_data *file_data, const char *data, >> bp = streamer_read_bitpack (&ib); >> if (info) >> { >> - info->inlinable = bp_unpack_value (&bp, 1); >> - info->fp_expressions = bp_unpack_value (&bp, 1); >> + info->inlinable = bp_unpack_value (&bp, 1); >> + /* On the side of streaming out, there is still one bit >> + streamed out between inlinable and fp_expressions bits, >> + which was used for cilk+ before but now always false. >> + To remove the bit packing need to bump LTO minor version, >> + so unpack a dummy bit here to keep consistent instead. */ >> + bp_unpack_value (&bp, 1); >> + info->fp_expressions = bp_unpack_value (&bp, 1); >> } >> else >> { >> - bp_unpack_value (&bp, 1); >> - bp_unpack_value (&bp, 1); >> + bp_unpack_value (&bp, 1); >> + bp_unpack_value (&bp, 1); >> + bp_unpack_value (&bp, 1); >> } >> >> count2 = streamer_read_uhwi (&ib); >>
diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c index 2470937460f..31199919405 100644 --- a/gcc/ipa-fnsummary.c +++ b/gcc/ipa-fnsummary.c @@ -4652,7 +4652,6 @@ ipa_fn_summary_write (void) info->time.stream_out (ob); bp = bitpack_create (ob->main_stream); bp_pack_value (&bp, info->inlinable, 1); - bp_pack_value (&bp, false, 1); bp_pack_value (&bp, info->fp_expressions, 1); streamer_write_bitpack (&bp); streamer_write_uhwi (ob, vec_safe_length (info->conds));