public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56726] i386: MALLOC_ABI_ALIGNMENT is too small (usually)
Date: Thu, 02 Apr 2015 11:36:00 -0000	[thread overview]
Message-ID: <bug-56726-4-AGcN81RacN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56726-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56726

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #9 from Florian Weimer <fweimer at redhat dot com> ---
On x86-64, Both jemalloc and tcmalloc return 8 byte aligned pointers for sizes
of 8 and less.  It's not true that malloc guarantuees 16-byte alignment there. 
You cannot look at glibc malloc implementation details and infer ABI properties
from that.


  parent reply	other threads:[~2015-04-02 11:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 19:11 [Bug target/56726] New: " chip at pobox dot com
2013-03-25 20:04 ` [Bug target/56726] " hjl.tools at gmail dot com
2013-03-25 21:35 ` chip at pobox dot com
2013-03-25 22:07 ` hjl.tools at gmail dot com
2013-03-25 22:36 ` chip at pobox dot com
2013-03-26 14:27 ` rguenth at gcc dot gnu.org
2013-03-29  6:05 ` chip at pobox dot com
2013-09-05 20:05 ` chip at pobox dot com
2014-06-12 17:11 ` chip at pobox dot com
2015-04-02 11:36 ` fweimer at redhat dot com [this message]
2015-04-02 11:53 ` jakub at gcc dot gnu.org
2015-04-02 21:48 ` chip at pobox dot com
2015-04-06 16:28 ` fweimer at redhat dot com

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=bug-56726-4-AGcN81RacN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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. 
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).