public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64798] [5 regression] g++.old-deja/g++.eh/badalloc1.C FAILs
Date: Mon, 26 Jan 2015 15:45:00 -0000 [thread overview]
Message-ID: <bug-64798-4-iJGUbmw3VO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64798-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64798
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from rguenther at suse dot de <rguenther at suse dot de> ---
[...]
> Does malloc return 8-byte aligned memory? Is __alignof__
It does, according to libc sources exactly for the case at hand:
* Alignment (ALIGN) changed to 8 for SPARC ldd/std.
> struct free_entry {
> std::size_t size;
> free_entry *next;
> };
>
> less than 8?
Yup: 4 in the (failing) 32-bit case.
Rainer
next prev parent reply other threads:[~2015-01-26 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:52 [Bug libstdc++/64798] New: " ro at gcc dot gnu.org
2015-01-26 13:53 ` [Bug libstdc++/64798] " ro at gcc dot gnu.org
2015-01-26 15:00 ` rguenther at suse dot de
2015-01-26 15:02 ` rguenther at suse dot de
2015-01-26 15:23 ` rguenth at gcc dot gnu.org
2015-01-26 15:45 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2015-01-27 10:58 ` rguenth at gcc dot gnu.org
2015-01-27 12:10 ` jakub at gcc dot gnu.org
2015-01-27 12:16 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-01-27 12:27 ` rguenther at suse dot de
2015-01-27 12:31 ` rguenth at gcc dot gnu.org
2015-01-27 12:33 ` jakub at gcc dot gnu.org
2015-01-27 12:38 ` rguenther at suse dot de
2015-01-27 12:40 ` rguenth at gcc dot gnu.org
2015-01-27 12:42 ` jakub at gcc dot gnu.org
2015-01-27 12:51 ` rguenther at suse dot de
2015-01-27 12:52 ` jakub at gcc dot gnu.org
2015-01-28 9:54 ` rguenth at gcc dot gnu.org
2015-01-28 10:01 ` rguenth at gcc dot gnu.org
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-64798-4-iJGUbmw3VO@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).