public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Ondřej Bílka" <neleai@seznam.cz>
To: dhatch at ilm dot com <sourceware-bugzilla@sourceware.org>
Cc: glibc-bugs@sourceware.org
Subject: Re: [Bug dynamic-link/15311] New: _dl_sort_fini static deps can be violated by dynamic ones
Date: Wed, 27 Mar 2013 22:09:00 -0000	[thread overview]
Message-ID: <20130327220418.GA4410@domone.kolej.mff.cuni.cz> (raw)
In-Reply-To: <bug-15311-131@http.sourceware.org/bugzilla/>

On Wed, Mar 27, 2013 at 07:49:25AM +0000, dhatch at ilm dot com wrote:
> http://sourceware.org/bugzilla/show_bug.cgi?id=15311
> 
>              Bug #: 15311
>            Summary: _dl_sort_fini static deps can be violated by dynamic
>                     ones
>            Product: glibc
>            Version: unspecified
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: dynamic-link
>         AssignedTo: unassigned@sourceware.org
>         ReportedBy: dhatch@ilm.com
>     Classification: Unclassified
> 
> 
> _dl_sort_fini tries to honor static dependencies
> at the expense of relocation (dynamic) dependencies, when there is a conflict.
> But the code that does this is rather half-hearted--
> it only ignores a dynamic dependency
> if the dynamic dependency directly contradicts
> a single static dependency, per the following comment
> in the loop over dynamic dependencies in elf/dl-fini.c:
>     /* If a cycle exists with a link time dependency,
>        preserve the latter.  */  
> 
> In even slightly more complex situations,
> e.g. a mixed cycle of length 3 (consisting of at least one 
> static and at least one dynamic dependency),
> no preference is given to the static dep(s);
> the cycle is broken arbitrarily and so the static dep may be violated,
> even if there are no cycles at all in the static dependency graph.
> 
> If static dependencies really are more important than dynamic ones,
> it might be a good idea to give them preference in a more principled way.
> 
> If the sorting routine gets overhauled
> (as I think it needs to be, due to currently absurd asymptotic behavior,
> see bug 15310)
> it would be good to keep this in mind.
> 
If you do topologic sort it should suffice to take static dependency
edges before dynamic ones, it assures that static when static are acyclic then
they are always correctly ordered.


  parent reply	other threads:[~2013-03-27 22:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27  7:49 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 ` Ondřej Bílka [this message]
2013-03-27 22:09 ` neleai at seznam dot cz
2013-03-27 22:40 ` 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
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=20130327220418.GA4410@domone.kolej.mff.cuni.cz \
    --to=neleai@seznam.cz \
    --cc=glibc-bugs@sourceware.org \
    --cc=sourceware-bugzilla@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).