public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth.at.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug boehm-gc/66848] boehm-gc fails test suite on x86_64-apple-darwin15
Date: Sun, 18 Oct 2015 16:57:00 -0000 [thread overview]
Message-ID: <bug-66848-4-NSdY5aydrq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66848-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66848
--- Comment #20 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
Also, the one commonality in all of the boehm-gc regressions on darwin15
(against the Apple Clang 7.0 compiled libunwind.dylib) is instances of...
* thread #1: tid = 0x20dbb8, 0x00007fff93f37148 libdyld.dylib`dyld_stub_binder,
queue = 'com.apple.main-thread', stop reason = instruction step into
frame #0: 0x00007fff93f37148 libdyld.dylib`dyld_stub_binder
libdyld.dylib`dyld_stub_binder:
-> 0x7fff93f37148 <+0>: pushq %rbp
0x7fff93f37149 <+1>: testq $0xf, %rsp
0x7fff93f37150 <+8>: jne 0x7fff93f372da ;
stack_not_16_byte_aligned_error
errors. The fact that hacking the ALIGNMENT setting in
boehm-gc/include/private/gcconfig.h to use 2 eliminates the regressions would
seem to make sense then as this would be forcing everything to be 16-bit
aligned.
prev parent reply other threads:[~2015-10-18 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 13:59 [Bug boehm-gc/66848] New: " howarth.at.gcc at gmail dot com
2015-07-12 14:02 ` [Bug boehm-gc/66848] " howarth.at.gcc at gmail dot com
2015-07-12 15:49 ` howarth.at.gcc at gmail dot com
2015-07-12 15:50 ` howarth.at.gcc at gmail dot com
2015-07-12 15:59 ` howarth.at.gcc at gmail dot com
2015-07-12 16:09 ` howarth.at.gcc at gmail dot com
2015-07-12 16:16 ` howarth.at.gcc at gmail dot com
2015-09-23 16:06 ` howarth.at.gcc at gmail dot com
2015-10-11 15:54 ` howarth.at.gcc at gmail dot com
2015-10-11 19:45 ` howarth.at.gcc at gmail dot com
2015-10-14 16:39 ` mrs at gcc dot gnu.org
2015-10-14 21:17 ` howarth.at.gcc at gmail dot com
2015-10-15 19:26 ` howarth.at.gcc at gmail dot com
2015-10-15 19:37 ` howarth.at.gcc at gmail dot com
2015-10-15 20:43 ` jeremyhu at macports dot org
2015-10-16 1:48 ` howarth.at.gcc at gmail dot com
2015-10-16 6:44 ` howarth.at.gcc at gmail dot com
2015-10-18 16:46 ` howarth.at.gcc at gmail dot com
2015-10-18 16:57 ` howarth.at.gcc at gmail dot com [this message]
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-66848-4-NSdY5aydrq@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).