unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Wolfgang Jenkner <wjenkner@inode.at>
To: markus@trippelsdorf.de
Cc: eggert@cs.ucla.edu, 24065@debbugs.gnu.org
Subject: bug#24065: commit 09ece4d341a7 (Restore the calloc family) causes miscompile for gcc-5 and higher
Date: Mon, 25 Jul 2016 17:48:50 +0200	[thread overview]
Message-ID: <579634e2.pR6ELx3DWCEAJiKN%wjenkner@inode.at> (raw)
In-Reply-To: <20160725142414.GD315@x4>

Markus Trippelsdorf <markus@trippelsdorf.de> wrote:

> > > This happens on a Gentoo system (glibc trunk, gcc-6 latest branch):

> But version 24.5 is the latest stable release. 
> It is sad, that it cannot be compiled with gcc-5 or gcc-6.

Actually, on GNU/Linux src/gmalloc.c (which contains the code in
question) is not even compiled, normally.

The reason for your compilation troubles seems to be that you use
a recent git checkout of glibc (as you stated above) which I guess
already contains

http://repo.or.cz/glibc.git/commitdiff/2ba3cfa1607c36613f3b30fb1ae4ec530245ce64

IIUC, this commit removes  the declaration of __malloc_initialize_hook,
so the emacs configure check for "whether malloc is Doug Lea style"
will fail.

And this is the reason why you suddenly need malloc etc. from
src/gmalloc.c.







  reply	other threads:[~2016-07-25 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  7:22 bug#24065: commit 09ece4d341a7 (Restore the calloc family) causes miscompile for gcc-5 and higher Markus Trippelsdorf
2016-07-25 12:38 ` Wolfgang Jenkner
2016-07-25 12:55   ` Markus Trippelsdorf
2016-07-25 13:27     ` Wolfgang Jenkner
2016-07-25 14:24       ` Markus Trippelsdorf
2016-07-25 15:48         ` Wolfgang Jenkner [this message]
2016-07-25 15:58           ` Markus Trippelsdorf
2016-07-26  7:08           ` 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=579634e2.pR6ELx3DWCEAJiKN%wjenkner@inode.at \
    --to=wjenkner@inode.at \
    --cc=24065@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=markus@trippelsdorf.de \
    /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).