https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #13 from Murugesan Nagarajan ---
@Andrew,
Thank you for updating current bug id: 94810
Old bug reported:
On: Mon 27-Apr-2020 09:44:52 PM UTC
Old Bug URL:
https://gcc.gnu.org/bugzi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #12 from Murugesan Nagarajan ---
Thank you for sharing comment at:
>> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=4e4e3ffd10f53e
Move stream initialization into compiled library
I am facing my issue to have my proper environment:
0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #11 from Murugesan Nagarajan ---
Hi Andrew,
Thank you for your comment. I'll check this after 09:00 AM.
Regards,
N.Murugesan
Google:
murugesan openssl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #9 from Murugesan Nagarajan ---
I'll update my comment today(Sat 04-Feb-2023 IST) after 09:00 AM IST. Right now
I'm facing network issue due to travelling.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #7 from Geoffrey Casper ---
I believe I did misunderstand comment 3. Thanks for your clarification. Do all
global objects get marked with the constructor attribute, which leads to the
ambiguity?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #6 from Jonathan Wakely ---
Maybe you misunderstood comment 3, the construction order is only unspecified
when you use __attribute__((constructor)). If you just create normal global
objects using normal C++ the order within a single t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #5 from Jonathan Wakely ---
I don't see how that could conform to the standard's requirements.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #4 from Geoffrey Casper ---
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'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #3 from Jonathan Wakely ---
There isn't, there's a segfault in your program. That is caused by assuming
that the global streams have been constructed already, when it is clearly
documented that the construction order is unspecified.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #2 from Geoffrey Casper ---
I suppose that's a workaround, but there shouldn't be a seg fault in a
libstdc++ header file.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94810
--- Comment #1 from Jonathan Wakely ---
Why can't you just use a global object with a constructor and destructor? That
would get correctly ordered with respect to the std::ios_base::Init object that
needs to be created before std::cout can be use
13 matches
Mail list logo
