public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: "Galloway, Greg (ISSAtlanta)" <GGalloway@iss.net>,
	Rahul Parasnis <rahul.parasnis@creditlyonnais.fr>,
	gcc <gcc@gcc.gnu.org>
Subject: Re: Support
Date: Tue, 01 Feb 2000 20:20:00 -0000	[thread overview]
Message-ID: <519.949464944@upchuck> (raw)
In-Reply-To: <orzotktfmp.fsf@garnize.lsd.ic.unicamp.br>

  In message < orzotktfmp.fsf@garnize.lsd.ic.unicamp.br >you write:
  > On Jan 31, 2000, Jeffrey A Law <law@cygnus.com> wrote:
  > 
  > >   In message <DF3CC311E898D311A3670008C709BD232EE970@msgatl01.iss.net>you
  >  write:
  > 
  > >> How about gas from binutils-2.9.1?
  > 
  > > Unknown.  Probably yes since I don't remember any hpux11 specific
  > > assembler issues.
  > 
  > No changes for 64bit support?  I assume this has been introduced in
  > HP/UX 11, but this assumption may be totally off-base, since only
  > recently I have gained guest access to an HP/UX machine.
64bit ELF is a completely separate issue.  hpux11 also has a 32bit SOM mode
just like earlier versions of hpux.
jeff

  reply	other threads:[~2000-02-01 20:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-31 12:44 Support Galloway, Greg (ISSAtlanta)
2000-01-31 12:48 ` Support Alexandre Oliva
2000-01-31 22:31   ` Support Russ Allbery
2000-01-31 16:12 ` Support Jeffrey A Law
2000-02-01 20:03   ` Support Alexandre Oliva
2000-02-01 20:20     ` Jeffrey A Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09  9:32 Support rajrao
2000-02-01  7:06 Support Galloway, Greg (ISSAtlanta)
2000-02-01  1:37 Support Rahul Parasnis
2000-02-01  8:57 ` Support Joe Buck
2000-02-01 20:08 ` Support Alexandre Oliva
2000-01-30 21:41 Support N8TM
2000-01-30 20:40 Support Rahul Parasnis
2000-01-30 20:59 ` Support Alexandre Oliva

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=519.949464944@upchuck \
    --to=law@cygnus.com \
    --cc=GGalloway@iss.net \
    --cc=gcc@gcc.gnu.org \
    --cc=oliva@lsd.ic.unicamp.br \
    --cc=rahul.parasnis@creditlyonnais.fr \
    /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).