Linux PARISC architecture development
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Ding dong, reserved %r8 is dead
Date: 06 Jul 2000 18:03:40 -0400	[thread overview]
Message-ID: <87em56or0j.fsf@linuxcare.com> (raw)

As of this afternoon, the GCC in puffin.external.hp.com CVS no longer
reserves %r8.  You will need to get binutils-2.10 or your builds will
be broken.  I've built a successful kernel+palo lifimage with this
GCC, but haven't tested glibc or userspace yet due to reasons
mentioned below, and the fact that I have been also working on merging
our GCC forward to the mainline CVS version (the *real* 2.96 :-)

One other thing - USE_CONST_SECTION is no longer defined to 0, so GCC
will put strings and such in a .rodata section.  I'm not sure why we
were avoiding this in the past - was it a SOM-ism?

I guess there's no good reason not to have read-only data in the text
section, aside from the fact that it makes reading objdump output a
bit confusing, so we can change it back if there is a pressing reason.

Oh, and for a few hours, glibc builds were slightly broken because GCC
was not building crt{begin,end}.o, for reasons that are beyond me.
I've manually added them in GCC's configure.in, and it should build
again.

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

             reply	other threads:[~2000-07-06 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-06 22:03 David Huggins-Daines [this message]
2000-07-06 22:27 ` [parisc-linux] Ding dong, reserved %r8 is dead Jeffrey A Law

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=87em56or0j.fsf@linuxcare.com \
    --to=dhd@linuxcare.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