public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egall at gwmail dot gwu.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66521] xgcc: cc1plus segfaults when compiling libstdc++-v3/src/c++11/ostream-inst.cc
Date: Sun, 30 Aug 2015 18:38:00 -0000	[thread overview]
Message-ID: <bug-66521-4-9lQFvWiFeL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66521-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Eric Gallager <egall at gwmail dot gwu.edu> ---
Created attachment 36272
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36272&action=edit
assembly that darwin 9 assembler rejects

Here's a snippet from the attached file for some of the lines around the one in
the error message from the previous comment (for context):

LHOTE93:
        .private_extern
__ZN4_VTVIN9__gnu_cxx24__concurrence_wait_errorEE12__vtable_mapE
        .no_dead_strip
__ZN4_VTVIN9__gnu_cxx24__concurrence_wait_errorEE12__vtable_mapE
        .globl __ZN4_VTVIN9__gnu_cxx24__concurrence_wait_errorEE12__vtable_mapE
        .weak_definition
__ZN4_VTVIN9__gnu_cxx24__concurrence_wait_errorEE12__vtable_mapE
        .align 2
__ZN4_VTVIN9__gnu_cxx24__concurrence_wait_errorEE12__vtable_mapE:
        .space 4
        .private_extern
__ZN4_VTVIN9__gnu_cxx29__concurrence_broadcast_errorEE12__vtable_mapE
        .no_dead_strip
__ZN4_VTVIN9__gnu_cxx29__concurrence_broadcast_errorEE12__vtable_mapE
        .globl
__ZN4_VTVIN9__gnu_cxx29__concurrence_broadcast_errorEE12__vtable_mapE
        .weak_definition
__ZN4_VTVIN9__gnu_cxx29__concurrence_broadcast_errorEE12__vtable_mapE
        .align 2


      parent reply	other threads:[~2015-08-30 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 13:42 [Bug bootstrap/66521] New: " egall at gwmail dot gwu.edu
2015-06-12 13:45 ` [Bug bootstrap/66521] " egall at gwmail dot gwu.edu
2015-07-05  4:04 ` egall at gwmail dot gwu.edu
2015-07-06 16:02 ` ctice at gcc dot gnu.org
2015-07-28 17:01 ` ctice at gcc dot gnu.org
2015-07-30 12:08 ` redi at gcc dot gnu.org
2015-07-30 12:11 ` redi at gcc dot gnu.org
2015-07-30 14:10 ` egall at gwmail dot gwu.edu
2015-07-31 15:25 ` egall at gwmail dot gwu.edu
2015-08-05 18:41 ` egall at gwmail dot gwu.edu
2015-08-05 18:44 ` egall at gwmail dot gwu.edu
2015-08-07 23:18 ` cmtice at google dot com
2015-08-12 15:40 ` ctice at gcc dot gnu.org
2015-08-30 18:21 ` egall at gwmail dot gwu.edu
2015-08-30 18:38 ` egall at gwmail dot gwu.edu [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-66521-4-9lQFvWiFeL@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).