public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcasper42 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94810] std::cout segmentation fault in __attribute__((constructor)) function
Date: Tue, 28 Apr 2020 13:16:44 +0000	[thread overview]
Message-ID: <bug-94810-4-Kux49M5Hqe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94810-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Geoffrey Casper <gcasper42 at gmail dot com> ---
Wouldn't it make more sense to initialize global objects on a per need basis?
So the constructors of unused global objects would never be called and there is
no ambiguity of when constructors are called. I'd gladly work on implementing
this, but I'd need some more information on the brod design of GCC.

  parent reply	other threads:[~2020-04-28 13:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 21:44 [Bug libstdc++/94810] New: " gcasper42 at gmail dot com
2020-04-27 22:32 ` [Bug libstdc++/94810] " redi at gcc dot gnu.org
2020-04-27 23:41 ` gcasper42 at gmail dot com
2020-04-28  8:51 ` redi at gcc dot gnu.org
2020-04-28 13:16 ` gcasper42 at gmail dot com [this message]
2020-04-28 16:07 ` redi at gcc dot gnu.org
2020-04-28 16:09 ` redi at gcc dot gnu.org
2020-04-28 17:39 ` gcasper42 at gmail dot com
2020-04-28 20:52 ` redi at gcc dot gnu.org
2023-02-03 19:29 ` murugesandins at gmail dot com
2023-02-03 19:47 ` pinskia at gcc dot gnu.org
2023-02-03 22:04 ` murugesandins at gmail dot com
2023-02-04  3:22 ` murugesandins at gmail dot com
2023-02-06  4:41 ` murugesandins at gmail 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-94810-4-Kux49M5Hqe@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).