public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "w dot northcott at unsw dot edu dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/16787] NAN constant "(0.0/0.0)" cannot be compiled by Tru64 cc Date: Mon, 14 Feb 2005 10:27:00 -0000 [thread overview] Message-ID: <20050213225548.5488.qmail@sourceware.org> (raw) In-Reply-To: <20040727192305.16787.scott.bailey@eds.com> ------- Additional Comments From w dot northcott at unsw dot edu dot au 2005-02-13 22:55 ------- This is a documentation problem. The current host specific docs at http://gcc.gnu.org/install/ specific.html#alpha*-*-* read: ***************************** In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not currently (2001-06-13) work with mips-tfile. As a workaround, we need to use the old assembler, invoked via the barely documented -oldas option. To bootstrap GCC, you either need to use the Compaq C Compiler: % CC=cc srcdir/configure [options] [target] or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: % CC=gcc -Wa,-oldas srcdir/configure [options] [target] ***************************** This is misleading and unhelpful: 1. The only effect most people will observe from the assembler change is that gcc binaries built on older (pre 5.1) versions of Tru64 will not run on 5.1. 2. The -oldas seems to be unecessary. 3. The -ieee flag is vital to bootstrap using the DEC compiler. So the configure suggestion should read: 'To bootstrap GCC, you either need to use the Compaq C Compiler: % CC="cc -ieee" srcdir/configure [options] [target]' Could someone please please fix the documentation. Bill Northcott -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16787
next prev parent reply other threads:[~2005-02-13 22:55 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-27 19:23 [Bug bootstrap/16787] New: " scott dot bailey at eds dot com 2004-07-28 6:07 ` [Bug bootstrap/16787] " pinskia at gcc dot gnu dot org 2004-07-28 14:12 ` scott dot bailey at eds dot com 2004-07-28 19:30 ` scott dot bailey at eds dot com 2004-07-29 11:44 ` falk at debian dot org 2004-07-29 14:02 ` scott dot bailey at eds dot com 2004-07-30 14:54 ` scott dot bailey at eds dot com 2004-09-02 13:54 ` pinskia at gcc dot gnu dot org 2004-09-09 17:04 ` pinskia at gcc dot gnu dot org 2005-02-14 10:27 ` w dot northcott at unsw dot edu dot au [this message] 2005-05-15 1:08 ` pinskia at gcc dot gnu dot org [not found] <bug-16787-6578@http.gcc.gnu.org/bugzilla/> 2005-11-23 15:04 ` pinskia at gcc dot gnu dot org 2006-02-11 16:50 ` sayle at gcc dot gnu dot org 2006-02-16 16:45 ` sayle at gcc dot gnu dot org 2006-02-16 17:43 ` pinskia at gcc dot gnu dot org 2006-02-16 20:15 ` sayle at gcc dot gnu dot org 2006-02-16 20:17 ` pinskia at gcc dot gnu dot org 2006-02-17 1:13 ` sayle at gcc dot gnu dot org 2006-02-17 1:21 ` pinskia at gcc dot gnu dot org
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=20050213225548.5488.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).