public inbox for
 help / color / mirror / Atom feed
From: Thomas Schwinge <>
To: <>, Jonathan Wakely <>
Subject: libstdc++ "freestanding" ('--disable-hosted-libstdcxx') with '-fno-rtti', '-fno-exceptions': 'libstdc++-v3/libsupc++/' global constructors
Date: Thu, 14 Jul 2022 13:54:15 +0200	[thread overview]
Message-ID: <> (raw)


In context of <> '[OpenMP][AMDGCN][nvptx]
C++ offloading: unresolved _Znwm = "operator new(unsigned long)"'
I'm looking into building GCN, nvptx offloading libstdc++ "freestanding"
('--disable-hosted-libstdcxx') with '-fno-rtti', '-fno-exceptions'.
(I've basically got these things wired up; details to be shared later.)

For nvptx, I'm running into:

    In function ‘(static initializers for [...]/libstdc++-v3/libsupc++/’:
    cc1plus: sorry, unimplemented: global constructors not supported on this target
    make[4]: *** [Makefile:777: eh_alloc.lo] Error 1

... because, indeed, "global constructors not supported" for nvptx at
this time.  This may change, but I'd first like to get clarified
conceptually to which extent 'libstdc++-v3/libsupc++/' is
actually relevant for such a libstdc++ configuration, and/or whether this
should be expected to compile fine already?  Do certain things simply
need to be '#if'-conditionalized, or similar, for example?  I've not yet
looked into the details; hoping that's maybe easy for you to answer?

Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

             reply	other threads:[~2022-07-14 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 11:54 Thomas Schwinge [this message]
2022-07-14 15:25 ` Jonathan Wakely

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).