public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dave Cuthbert <dacut@neolinear.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/7882: HP bootstrap failure when building on PA 2.0 for  PA 1.1
Date: Tue, 10 Sep 2002 10:56:00 -0000	[thread overview]
Message-ID: <20020910175601.23680.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/7882; it has been noted by GNATS.

From: Dave Cuthbert <dacut@neolinear.com>
To: law@redhat.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/7882: HP bootstrap failure when building on PA 2.0
 for  PA 1.1
Date: Tue, 10 Sep 2002 13:52:24 -0400

 Jeff Law wrote:
 > Note that the PA port generates PA1.1 code unless you explicitly ask for
 > PA2.0 code via the -mpa-risc-2-0 runtime switch.
 > 
 > So you really shouldn't need to do anything special to generate PA1.1 code,
 > and in fact, by trying to do something special (configure for hppa1.1-hpux)
 > you've confused the compiler into thinking it's building cross tools which
 > is the root cause of your link time failures.
 
 Ah, thanks for this info.
 
 We got burned by the HP compiler here (we have PA2.0 machines only, and 
 one of our beta releases failed at a customer site which had PA1.1 
 machines), so I was being paranoid.
 
 Dave
 


             reply	other threads:[~2002-09-10 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 10:56 Dave Cuthbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 12:46 David Cuthbert
2003-05-14 10:56 giovannibajo
2003-05-14  9:36 Dara Hazeghi
2002-09-10 11:16 Jeff Law
2002-09-10 10:46 Jeff Law
2002-09-10  9:56 dacut

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=20020910175601.23680.qmail@sources.redhat.com \
    --to=dacut@neolinear.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).