zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Fwd: 5.8: LTO exposes some new issues
Date: Sat, 25 Jul 2020 13:05:47 -0700	[thread overview]
Message-ID: <CAH+w=7Z0oDO18u7uRVoOhjG0-0ydvi65zt2mMHD_wb636C9F1w@mail.gmail.com> (raw)
In-Reply-To: <CABB28CxSD5w-SY-iCVYuQ4kJfBpNJOWhpk4HOrS1DNPfMVztgw@mail.gmail.com>

I am not likely to pursue this further, I don't have a suitable build
environment.

---------- Forwarded message ---------
From: Tomasz Kłoczko <kloczko.tomasz@gmail.com>
Date: Sat, Jul 25, 2020 at 11:59 AM
Subject: Re: 5.8: LTO exposes some new issues
To: Bart Schaefer <schaefer@brasslantern.com>


On Sat, 25 Jul 2020 at 18:43, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Tue, Jul 21, 2020 at 11:00 PM Daniel Shahaf <d.s@daniel.shahaf.name> 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 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
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

  parent reply	other threads:[~2020-07-25 20:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 23:41 Tomasz Kłoczko
2020-07-22  5:59 ` Daniel Shahaf
2020-07-25 17:43   ` Bart Schaefer
     [not found]     ` <CABB28CxSD5w-SY-iCVYuQ4kJfBpNJOWhpk4HOrS1DNPfMVztgw@mail.gmail.com>
2020-07-25 20:05       ` Bart Schaefer [this message]
2020-07-27  2:12         ` Fwd: " Daniel Shahaf
2020-07-27 10:07           ` Tomasz Kłoczko
2020-07-27 11:09             ` Roman Perepelitsa
2020-07-27 12:19               ` Roman Perepelitsa
2020-07-27 12:46                 ` Tomasz Kłoczko
2020-07-27 14:13                   ` Roman Perepelitsa
2020-07-27 14:19                   ` Roman Perepelitsa
2020-07-28  8:09                     ` Daniel Shahaf
2020-07-28 10:55                     ` Fwd: " Roman Perepelitsa
2020-07-28  8:19                   ` Daniel Shahaf
2020-07-28  7:53                 ` Daniel Shahaf
2020-07-28  8:25                   ` Peter Stephenson
2020-07-28 10:52                     ` Roman Perepelitsa
2020-07-28 11:19                       ` Daniel Shahaf
2020-07-28 11:31                         ` Roman Perepelitsa
2020-07-28 11:51                           ` Daniel Shahaf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7Z0oDO18u7uRVoOhjG0-0ydvi65zt2mMHD_wb636C9F1w@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).