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 8067 invoked from network); 25 Jul 2020 20:06:49 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 25 Jul 2020 20:06:49 -0000 Received: (qmail 22786 invoked by alias); 25 Jul 2020 20:06:37 -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: 46262 Received: (qmail 29745 invoked by uid 1010); 25 Jul 2020 20:06:37 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot1-f50.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25877. spamassassin: 3.4.4. Clear:RC:0(209.85.210.50):SA:0(-1.9/5.0):. Processed in 3.772812 secs); 25 Jul 2020 20:06:37 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.210.50 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=TUNPsbdJH0TZxsWev4R+uFhwcnjuPkNw22W5Ejf9eU8=; b=cmnofcodjN9HtHuMt4u6e21fZNGB5IguMlEvSDklJdj1/tXNOyujfbOwQZAXykXZCs J68MLJuEwUcTkzFtE/skI7jDj7CXFv5kQ3nr3+xFu0m8M4GWdSPB42m6B4mcwmlO7dcS cDdGW24aIxjbVDMdZKWdeGDnaBK8lIxogbaswGGMZj721QWXuvwzZO6VkQ3MDzMp5/HF 9XjkM8W/XKS5a/+FSXYJCl4lt+F9fItC4bSQB4ZWpKffOKFjZ5lrJGNv4yI09EM0rqwJ nloi5p/jHzTuE/XBv2Jtc9prYaaoZz8Ki/JAAdKDH/KTmdKgNkLZErPvWwg2A+vPS9sC Keng== X-Gm-Message-State: AOAM531lFqWiVykEyxIMb4Y6HPmdTSxNUHV2AlOAPQSlqP+P1oFdevgk ZIHBNbRFFN/+4KdNQQjDfjAFrKdIh2gX8IMEVGlhG8nL844= X-Google-Smtp-Source: ABdhPJw2mKLerk9Y0l4bUn12TxQHSB7Z8in8OE8hgpFEy49Phjpka7YKmrHskkb7zmPlPwFXOa6aDwMfMYQ2X9l8bxY= X-Received: by 2002:a9d:53c1:: with SMTP id i1mr4185987oth.161.1595707559113; Sat, 25 Jul 2020 13:05:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Sat, 25 Jul 2020 13:05:47 -0700 Message-ID: Subject: Fwd: 5.8: LTO exposes some new issues To: Zsh hackers list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am not likely to pursue this further, I don't have a suitable build environment. ---------- 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 On Sat, 25 Jul 2020 at 18:43, Bart Schaefer wro= te: > > On Tue, Jul 21, 2020 at 11:00 PM Daniel Shahaf w= rote: > > > > 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 looks > 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. 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. kloczek --=20 Tomasz K=C5=82oczko | LinkedIn: http://lnkd.in/FXPWxH