public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/15311] _dl_sort_fini static deps can be violated by dynamic ones
Date: Thu, 28 Mar 2013 08:19:00 -0000 [thread overview]
Message-ID: <bug-15311-131-AyLRN2OQy2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15311-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15311
--- Comment #8 from Ondrej Bilka <neleai at seznam dot cz> 2013-03-28 08:19:12 UTC ---
I realized it matters in which order we consider dependencies. Naturaly
dynamic deps come after static.
Why should we simply add timestamp when object is created and use it to
call destructors in reverse order.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-03-28 8:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 7:49 [Bug dynamic-link/15311] New: " dhatch at ilm dot com
2013-03-27 8:46 ` [Bug dynamic-link/15311] " dhatch at ilm dot com
2013-03-27 12:59 ` carlos at redhat dot com
2013-03-27 20:35 ` dhatch at ilm dot com
2013-03-27 22:09 ` neleai at seznam dot cz
2013-03-27 22:09 ` [Bug dynamic-link/15311] New: " Ondřej Bílka
2013-03-27 22:40 ` [Bug dynamic-link/15311] " dhatch at ilm dot com
2013-03-28 4:36 ` dhatch at ilm dot com
2013-03-28 5:00 ` dhatch at ilm dot com
2013-03-28 7:37 ` Ondřej Bílka
2013-03-28 7:37 ` neleai at seznam dot cz
2013-03-28 8:19 ` Ondřej Bílka
2013-03-28 8:19 ` neleai at seznam dot cz [this message]
2013-03-29 14:53 ` dhatch at ilm dot com
2014-06-13 18:36 ` fweimer at redhat dot com
2021-10-21 19:21 ` cvs-commit at gcc dot gnu.org
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-15311-131-AyLRN2OQy2@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).