public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Olaf van der Spek <olafvdspek@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: binutils@sourceware.org
Subject: Re: Support for automatic linking via pragma
Date: Fri, 04 Mar 2011 17:35:00 -0000	[thread overview]
Message-ID: <AANLkTin+p_L4z5kmy2Q6A7o3J-tKPhCpMmxu9Rx9iwmp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=7tb0uMfj54p0yEt+=jm-Rxf4+c6gOXPwD-82z@mail.gmail.com>

On Fri, Mar 4, 2011 at 6:31 PM, Kai Tietz <ktietz70@googlemail.com> wrote:
> I didn't found time to work on that in more detail for PE-COFF and
> indeed is for it the dependency-tree for objects/libraries the
> challenging part.
> As for doing this on each used object base, means we have on link-time
> a changing import dependency tree, as each object actual used could
> generate new one. This easily can lead to cycles and is IMHO too
> costy.
> So my research had shown that it would be more efficent (and not that
> complex), to pre-scan those directives before the actual link-phase
> and build up the object/library link dependency-tree once.
> The gcc pragma implementation would be straight-forward and obvious.

I didn't consider this issue yet. I remember in the distant past I had
some issues with lib ordering, but in the recent past I didn't. Did
GCC avoid this issue or was I just lucky?
If it did avoid it, I assume that code can be reused.

-- 
Olaf

  reply	other threads:[~2011-03-04 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 18:17 Olaf van der Spek
2011-03-04 16:30 ` Olaf van der Spek
2011-03-04 16:44   ` H.J. Lu
2011-03-04 16:52     ` Ian Lance Taylor
2011-03-04 16:55       ` H.J. Lu
2011-03-04 17:31         ` Kai Tietz
2011-03-04 17:35           ` Olaf van der Spek [this message]
2011-03-04 18:40         ` Ian Lance Taylor
2011-03-04 17:31     ` Olaf van der Spek

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=AANLkTin+p_L4z5kmy2Q6A7o3J-tKPhCpMmxu9Rx9iwmp@mail.gmail.com \
    --to=olafvdspek@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ktietz70@googlemail.com \
    /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).