Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Paul Bame <bame@endor.fc.hp.com>
To: willy@thepuffingroup.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] new binutils/gcc
Date: Fri, 25 Feb 2000 14:12:17 -0700	[thread overview]
Message-ID: <E12OS25-0007l6-00@endor.fc.hp.com> (raw)
In-Reply-To: Your message of "Tue, 15 Feb 2000 03:09:46 EST." <20000215030946.V9944@thepuffingroup.com>


Willy, Sammy,

I've been trying the elf stuff plus Sammy's patches, updated to work
from the current CVS bits.  Here's what I've found so far:

1) this compiler seems to allocate the rp and ret1 registers first
which makes debugging from register dumps worse -- no glancing at r2
to figure out who called ya.

2) I'm seeing death in an infinite loop in flush_instruction_tlb and
it looks as though it's because cache_info has not been initialized yet.

3) We get to start_parisc() but no C procedure calls work from there --
even a local call is failing.  The local call, to address c0114dd4,
generates the following branch:

    c020cbcc:       e5 00 29 38     be,l 49c(sr4,r8)

r8 = 0xc0000000 and sr4 = 0 so I think this branches to a very
bad place.  Another branch to pdc_console_init() generates

    c020cbec:       e5 00 31 30     be,l 898(sr4,r8)

pdc_console_init is at c0101b50 T pdc_console_init

Note that I CHANGED the load address of 0xc0010000 to 0xc0100000 in
vmlinux.lds but I can't see there's a relationship so I'm stumped and
suspect maybe a language system bug which isn't my forte.  Enjoy :-)

The sources I used can be generated by applying the patch
pehc:/tmp/sammy2 to the CVS bits current as of this morning.

	-Paul Bame

  reply	other threads:[~2000-02-25 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15  8:09 [parisc-linux] new binutils/gcc willy
2000-02-25 21:12 ` Paul Bame [this message]
2000-02-27 18:26   ` Sam Creasey
2000-02-29 23:06     ` Paul Bame
  -- strict thread matches above, loose matches on Subject: below --
2000-02-15  4:02 willy

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=E12OS25-0007l6-00@endor.fc.hp.com \
    --to=bame@endor.fc.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=willy@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