public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Heribert Dahms <heribert_dahms@icon-gmbh.de>
Cc: "'egcs@egcs.cygnus.com'" <egcs@egcs.cygnus.com>
Subject: Re: gcc/egcs 64bit pointers under HP-UX11 PA-RISC2.0
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <2755.937933516@upchuck.cygnus.com> (raw)
Message-ID: <19990930180200.hTlw7yeBCju_L_ghziQYpMQ8J-O4aj0PHu-X4S1Oh9s@z> (raw)
In-Reply-To: <99B82AA9708ED0119B55006097125A001E6061@ifk63.mach.uni-karlsruhe.de>

  In message <99B82AA9708ED0119B55006097125A001E6061@ifk63.mach.uni-karlsruhe.d
e>you write:
  > Hi,
  > 
  > searching for 'hpux11' on egcs.cygnus.com I found that
  > Cygnus donated some support June 29, 1999,
  > but that it will not be included in 2.95.
  > So I downloaded both gcc-2.95.1 and egcs-19990920,
  > browsed thru the ChangeLogs and gcc/config/pa,
  > put it seems there are still no 64bit pointers.
  > I need to go beyond 2GB total calloc'ed data soon,
  > but single structures will be < 2GB, so I guess I can use:
  > #define PTRDIFF_TYPE "int"
  > Do you have something even pre-alpha I could try 'as is'?
The existing hpux11 support is 32bit mode only.

I've done a 64bit port that Cygnus will contribute after we've received final
payment from our customer (gcc, gas, gld, binutils, the whole (*&@#$ thing).

jeff

  reply	other threads:[~1999-09-30 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-21  9:56 Heribert Dahms
1999-09-21 10:08 ` Jeffrey A Law [this message]
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Heribert Dahms
1999-09-21 10:41 Heribert Dahms
1999-09-30 18:02 ` Heribert Dahms

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=2755.937933516@upchuck.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=heribert_dahms@icon-gmbh.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).