From: Jeffrey A Law <law@cygnus.com>
To: Alex deVries <adevries@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Sat, 12 Jun 1999 00:32:23 -0600 [thread overview]
Message-ID: <22030.929169143@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Sat, 12 Jun 1999 01:42:13 EDT. <3761F335.ADA76678@thepuffingroup.com>
In message <3761F335.ADA76678@thepuffingroup.com>you write:
> This is a multi-part message in MIME format.
> > Then search for $CODE$ in the resulting /tmp/BLAH. We'll work backwards
> from
> > what you find.
>
> The offending files are:
>
> ipl_c.o: file format elf32-hppa
[ ... ]
> 4 $CODE$ 00000210 00000000 00000000 000002b0 2**3
> CONTENTS, ALLOC, LOAD, RELOC, CODE
> 5 $CODE$ 000001f8 00000000 00000000 000004c0 2**3
> CONTENTS, ALLOC, LOAD, RELOC, CODE
> 6 $CODE$ 000003d8 00000000 00000000 000006b8 2**3
> CONTENTS, ALLOC, LOAD, RELOC, CODE
OK. This is actually enough to identify the problem.
This is one of those stupid problems that will go away when we revamp the tools
to do ELF in a more traditional fashion -- in particular dumping all the dumb
HP names for spaces/subspaces and sticking with standard names.
The problem is in the assembler's handling of .nsubspa. It is not honoring the
$CODE$ -> .text translation for that case.
in gas/tc-hppa.c::pa_subspace there should be code like this:
/* If this is an existing subspace, then we want to use the
segment already associated with the subspace.
FIXME NOW! ELF BFD doesn't appear to be ready to deal with
lots of sections. It might be a problem in the PA ELF
code, I do not know yet. For now avoid creating anything
but the "standard" sections for ELF. */
if (create_new)
section = subseg_force_new (ss_name, 0);
else if (ssd)
section = ssd->ssd_seg;
else if (alias)
section = subseg_new (alias, 0);
else if (!alias && USE_ALIASES)
{
as_warn (_("Ignoring subspace decl due to ELF BFD bugs."));
demand_empty_rest_of_line ();
return;
}
else
section = subseg_new (ss_name, 0);
You'll note the FIXME NOW!. It's about 5 years old :( Though it will be
zapped as we drop the $CODE$ nonsense.
Anyway I think you may be able to fix this bug by changing the subseg_force_new
call to look something like:
subseg_force_new (alias ? alias : ss_name, 0);
Though I'm a little confused. I thought y'all were dropping the existing ELF
stuff -- I would strongly recommend it. We're not even planning to keep the
existing elf32-hppa stuff building in gas/binutils as we work on the rewrite.
You're working with a totally dead and unsupported toolchain at this point.
jeff
next parent reply other threads:[~1999-06-12 6:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3761F335.ADA76678@thepuffingroup.com>
1999-06-12 6:32 ` Jeffrey A Law [this message]
1999-06-12 11:15 ` [parisc-linux] booting problems Alex deVries
1999-06-12 16:57 ` John David Anglin
1999-06-12 18:36 ` Alan Cox
1999-06-12 18:53 ` Jeffrey A Law
1999-06-12 19:36 ` Matthew Wilcox
1999-06-12 21:15 ` Jeffrey A Law
1999-06-12 21:09 ` Jeffrey A Law
1999-06-13 19:10 ` John David Anglin
1999-06-14 0:17 ` Alex deVries
2001-08-31 16:06 James Waterhouse
-- strict thread matches above, loose matches on Subject: below --
1999-06-11 18:49 Jason Eckhardt
1999-06-11 19:37 ` Alex deVries
1999-06-12 0:56 ` John David Anglin
1999-06-12 1:25 ` John David Anglin
1999-06-12 3:23 ` John David Anglin
1999-06-12 3:43 ` Jeffrey A Law
1999-06-12 5:10 ` Alex deVries
1999-06-12 5:11 ` Jeffrey A Law
1999-06-10 21:06 Richard J. Rauenzahn
[not found] <no.id>
1999-06-10 18:32 ` Stan Sieler
1999-06-10 5:07 Alex deVries
1999-06-10 6:20 ` Kirk Bresniker
1999-06-10 7:21 ` Alex deVries
1999-06-10 15:26 ` Kirk Bresniker
1999-06-10 17:08 ` Stan Sieler
1999-06-10 17:03 ` Stan Sieler
1999-06-10 21:20 ` John David Anglin
1999-06-11 7:36 ` Alex deVries
1999-06-11 8:57 ` Alex deVries
1999-06-11 9:08 ` Jeffrey A Law
1999-06-11 14:06 ` John David Anglin
1999-06-11 17:19 ` Alex deVries
1999-06-11 18:10 ` Kirk Bresniker
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=22030.929169143@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=adevries@thepuffingroup.com \
--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