From: Elric Milon <me@whirm.eu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Andy Moreton <andrewjmoreton@gmail.com>, 22522@debbugs.gnu.org
Subject: bug#22522: Commit b88e9cded7ae3756e3a2ec4a23e8df352a0239f9 breaks emacs dumping for me
Date: Tue, 02 Feb 2016 22:14:54 +0100 [thread overview]
Message-ID: <87vb66ddbl.fsf@carbon.whirm.eu> (raw)
In-Reply-To: <56B0E6B9.5020609@cs.ucla.edu>
Paul Eggert <eggert@cs.ucla.edu> writes:
> Thanks for reporting this. I reproduced the problem on Fedora 23 x86-64.
> It appears to be a bug in link-time optimization. The symbol
> __malloc_initialize_hook is marked external in alloc.o, but merely
> static (private) in temacs:
>
> $ nm -o alloc.o temacs | grep __malloc_init
> alloc.o:00000000002e0a40 D __malloc_initialize_hook
> temacs:0000000000b25340 d __malloc_initialize_hook
>
> We used to define this variable in emacs.o, and we now do it in alloc.o.
> Possibly we were lucky that the code ever worked, as I guess the LTO bug
> strikes depending on link time order.
>
> I installed the attached patch, which works around the bug for me.
> Please give it a try. Are any of you connected to the folks who
> implement LTO? It'd be nice to report this bug to them somehow.
I checked out latest master which appears to contain this patch and it's
building again.
Thanks!
--
Elric Milon
PGP: 3939C2B494084E2F | https://whirm.eu
next prev parent reply other threads:[~2016-02-02 21:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 13:37 bug#22522: Commit b88e9cded7ae3756e3a2ec4a23e8df352a0239f9 breaks emacs dumping for me Elric Milon
2016-02-01 22:27 ` Andy Moreton
2016-02-02 2:59 ` Ken Brown
2016-02-02 14:20 ` Wolfgang Jenkner
2016-02-02 14:36 ` Wolfgang Jenkner
2016-02-02 20:25 ` Ken Brown
2016-02-02 22:02 ` Andy Moreton
2016-02-02 22:32 ` Ken Brown
2016-02-02 22:08 ` Ken Brown
2016-02-02 22:54 ` Paul Eggert
2016-02-03 0:09 ` Ken Brown
2016-02-03 3:18 ` Ken Brown
2016-02-03 8:41 ` Paul Eggert
2016-02-03 13:35 ` Ken Brown
2016-02-03 14:01 ` Andy Moreton
2016-02-03 18:30 ` Ken Brown
2016-02-02 17:34 ` Paul Eggert
2016-02-02 18:28 ` Ken Brown
2016-02-02 17:26 ` Paul Eggert
2016-02-02 21:14 ` Elric Milon [this message]
2016-02-02 23:02 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb66ddbl.fsf@carbon.whirm.eu \
--to=me@whirm.eu \
--cc=22522@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=eggert@cs.ucla.edu \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).