Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Paul Bame <bame@fc.hp.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] where to put 64 bit libmilli?
Date: Tue, 02 Jan 2001 12:58:50 -0700	[thread overview]
Message-ID: <E14DXa6-0005xq-00@noam.fc.hp.com> (raw)
In-Reply-To: Your message of "Tue, 02 Jan 2001 14:39:03 EST." <200101021939.OAA07752@hiauly1.hia.nrc.ca>

= Last time I looked the 64 bit port was still using the same milli
= library as the 32 bit port.

Yes -- leading to some very surprising 64-bit kernel failures
before I found this "feature".  This is a 64-bit parisc linux gcc bug.

= Thus to integrate a 64 bit library,
= some work would have to be done to the machine description.  There
= are hooks to build asm code (see for example lib1funcs.asm and
= lib2funcs.asm in config/pa).

I've played with this a bit before -- I did the first ELF version of
of 32-bit millicode.  But I'm not at all certain we want to
keep millicode in libgcc.a since there's also some parisc linker magic to
automatically link millicode when required -- because some makefiles
using ld -r break (like the Linux kernel build) unless they're hacked to
include an explicit reference to libgcc.a.

= Has HP contributed this code to the public domain?  Probably, Jeff
= Law would be the one to contact to get integrated into the gcc mainline.

I have permission to sanitize and (L?)GPLize it.  I'm planning to
attempt the basic integration and then let Jeff or someone tell me
how I screwed it up :-)

	-Paul Bame

  reply	other threads:[~2001-01-02 19:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02 19:25 [parisc-linux] where to put 64 bit libmilli? Paul Bame
2001-01-02 19:39 ` John David Anglin
2001-01-02 19:58   ` Paul Bame [this message]
2001-01-02 20:17     ` Jeffrey A Law
2001-01-03  1:46       ` Alan Modra
2001-01-03  1:57         ` Matthew Wilcox
2001-01-03  2:34           ` Alan Modra
2001-01-03  3:37         ` Jeffrey A Law
2001-01-03  4:11           ` Alan Modra
2001-01-03  4:15             ` Jeffrey A Law
2001-01-03  4:44               ` Alan Modra
2001-01-04  4:04                 ` Jeffrey A Law
2001-01-04  5:20                   ` Alan Modra
2001-01-04  6:18                     ` John David Anglin
2001-01-04  7:03                       ` Alan Modra
2001-01-04 16:36                         ` Paul Bame
2001-01-04 17:06                           ` Jeffrey A Law
2001-01-04 17:29                       ` Jeffrey A Law
2001-01-04 17:37                     ` Jeffrey A Law
2001-01-04 17:41                       ` Paul Bame
2001-01-04 23:52                       ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2001-01-04 19:00 Cary Coutant
2001-01-04 19:15 ` Grant Grundler
2001-01-04 21:20 Cary Coutant

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=E14DXa6-0005xq-00@noam.fc.hp.com \
    --to=bame@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