From: Jeffrey A Law <law@cygnus.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: bame@debian.fc.hp.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Today's boot experience on a 735
Date: Tue, 16 Nov 1999 20:35:56 -0700 [thread overview]
Message-ID: <1129.942809756@upchuck> (raw)
In-Reply-To: Your message of Tue, 16 Nov 1999 21:48:51 EST. <199911170248.VAA15412@hiauly1.hia.nrc.ca>
In message <199911170248.VAA15412@hiauly1.hia.nrc.ca>you write:
> >
> > Create a .o file which contains a DLT & AFTERDLT section. Make sure the
> > DLT section appears first in the object file (I'm assuming they have the
> > same sort keys). Referece that .o first on the link line.
>
> As I noted, it appears to work as is.
Yea, but you appear to be depending on highly suspicious behavior. The
trick of ordering subspaces in the first .o on the link line to provide an
ordering for the subspaces in the final executable relies on documented
behavior of the HP linker.
> you know why the DLT section
> disappeared when I used the sort key of 255 for AFTERDLT? Although
> I haven't tried it, it may not be possible to create an object file with
> both DLT and AFTERDLT sections.
Not really. I do know that we had major problems with pxdb (post-link
processor
on HPs) mysteriously removing subspaces with sort keys of 255 in the past.
jeff
next prev parent reply other threads:[~1999-11-17 3:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-16 19:58 [parisc-linux] Today's boot experience on a 735 John David Anglin
1999-11-16 20:18 ` Paul Bame
1999-11-16 20:52 ` John David Anglin
1999-11-16 22:56 ` John David Anglin
1999-11-17 2:04 ` John David Anglin
1999-11-17 2:22 ` Jeffrey A Law
1999-11-17 2:48 ` John David Anglin
1999-11-17 3:35 ` Jeffrey A Law [this message]
1999-11-17 6:34 ` Philipp Rumpf
1999-11-17 18:12 ` John David Anglin
1999-11-17 20:54 ` Philipp Rumpf
1999-11-17 17:34 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
1999-11-20 0:57 Cary Coutant
1999-11-20 18:40 ` John David Anglin
1999-11-22 9:40 ` Philipp Rumpf
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=1129.942809756@upchuck \
--to=law@cygnus.com \
--cc=bame@debian.fc.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@thepuffingroup.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