From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16217 invoked from network); 27 Jul 2020 02:13:17 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 27 Jul 2020 02:13:17 -0000 Received: (qmail 8777 invoked by alias); 27 Jul 2020 02:13:06 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: Sender: zsh-workers@zsh.org X-Seq: 46263 Received: (qmail 18399 invoked by uid 1010); 27 Jul 2020 02:13:06 -0000 X-Qmail-Scanner-Diagnostics: from out2-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25884. spamassassin: 3.4.4. Clear:RC:0(66.111.4.26):SA:0(-2.6/5.0):. Processed in 4.301386 secs); 27 Jul 2020 02:13:06 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrheelgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenog fuuhhsphgvtghtffhomhgrihhnucdlgeelmdenucfjughrpefofgggkfgjfhffhffvufgt gfesthhqredtreerjeenucfhrhhomhepfdffrghnihgvlhcuufhhrghhrghffdcuoegurd hssegurghnihgvlhdrshhhrghhrghfrdhnrghmvgeqnecuggftrfgrthhtvghrnhepueeu gfegudetudehfedvtdeuiefhhffhleetledvvdekuddukeffieejtdeiiedunecuffhomh grihhnpehlnhhkugdrihhnnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepugdrshesuggrnhhivghlrdhshhgrhhgrfhdrnhgrmhgv X-ME-Proxy: X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-92-g11c785d-fm-20200721.004-g11c785d5 Mime-Version: 1.0 Message-Id: <35bf1c7b-163f-4baf-9d5a-c1d7e72459ec@www.fastmail.com> In-Reply-To: References: Date: Mon, 27 Jul 2020 02:12:03 +0000 From: "Daniel Shahaf" To: =?UTF-8?Q?Tomasz_K=C5=82oczko?= , "Zsh hackers list" Subject: Re: Fwd: 5.8: LTO exposes some new issues Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Tomasz, if you devise a patch for these issues, please post it so it can= be reviewed and applied. (If you prefer to wait for the Internet to write the patch you want, feel free to do so, but that strategy doesn't always work.) Cheers, Daniel Bart Schaefer wrote on Sat, 25 Jul 2020 20:05 +00:00: > I am not likely to pursue this further, I don't have a suitable build > environment. >=20 > ---------- Forwarded message --------- > From: Tomasz K=C5=82oczko > Date: Sat, Jul 25, 2020 at 11:59 AM > Subject: Re: 5.8: LTO exposes some new issues > To: Bart Schaefer >=20 >=20 > On Sat, 25 Jul 2020 at 18:43, Bart Schaefer wrote: > > > > On Tue, Jul 21, 2020 at 11:00 PM Daniel Shahaf wrote: > > > > > > Haven't looked at the other warnings you reported. > > > > They all appear to be clashes where the same pointer is declared > > "extern" in a header file but not so in the original source. It loo= ks > > as if the "mod_import_variable" preprocessor definition is supposed = to > > deal with this, perhaps it's not being properly defined in the > > situation where Tomasz is compiling. >=20 >=20 > Yes and they need to be resolved because even single such warnings and= > ld abandons applying LTO. > If you will decide which version should be used in both locations and > will have some patch for that please let me know about that because I > can test that kind of patch instantly proving that there is no other > coalition with LTO. >=20 > kloczek > --=20 > Tomasz K=C5=82oczko | LinkedIn: http://lnkd.in/FXPWxH >