From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Wolfgang Jenkner <wjenkner@inode.at>
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:58:40 +0200 [thread overview]
Message-ID: <20160725155840.GE315@x4> (raw)
In-Reply-To: <579634e2.pR6ELx3DWCEAJiKN%wjenkner@inode.at>
On 2016.07.25 at 17:48 +0200, Wolfgang Jenkner wrote:
> 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.
Thanks for finding the root cause.
I can confirm that my glibc versions contains the commit in question.
--
Markus
next prev parent reply other threads:[~2016-07-25 15:58 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
2016-07-25 15:58 ` Markus Trippelsdorf [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160725155840.GE315@x4 \
--to=markus@trippelsdorf.de \
--cc=24065@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=wjenkner@inode.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.