public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62100] c++11 threads invoke pure virtual function on arm embedded system
Date: Tue, 12 Aug 2014 10:05:00 -0000	[thread overview]
Message-ID: <bug-62100-4-r23HPd4IBf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62100-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2014-08-12
     Ever confirmed|0                           |1

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Those macros are only meant to be defined by the compiler, never by users.

If defining them fixes the problem it implies you are not compiling with the
same ABI as your libstdc++ was built with. I can't guess more than that because
you haven't provided any information on your target or how it was configured.

https://gcc.gnu.org/bugs/


  reply	other threads:[~2014-08-12 10:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 23:23 [Bug libstdc++/62100] New: " pab at pabigot dot com
2014-08-12 10:05 ` redi at gcc dot gnu.org [this message]
2014-08-12 11:27 ` [Bug target/62100] " pab at pabigot dot com
2014-08-12 11:50 ` redi at gcc dot gnu.org
2014-08-12 12:34 ` pab at pabigot dot com
2014-08-12 14:46 ` redi at gcc dot gnu.org
2014-08-14 14:03 ` pab at pabigot 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-62100-4-r23HPd4IBf@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).