public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scott dot bailey at eds dot com" <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: Fri, 30 Jul 2004 14:54:00 -0000	[thread overview]
Message-ID: <20040730145408.2611.qmail@sourceware.org> (raw)
In-Reply-To: <20040727192305.16787.scott.bailey@eds.com>


------- Additional Comments From scott dot bailey at eds dot com  2004-07-30 14:54 -------
Subject: RE:  NAN constant "(0.0/0.0)" cannot be comp
	iled by Tru64 cc

Okay, I was able to get a good bootstrap doing this:

CC="cc -ieee" CFLAGS=-O2 /usr/local/bin/make bootstrap

The semi-obvious alternative, 'CC=cc CFLAGS="-O2 -ieee" ...' does not work
because after the compiler build succeeds, the make process then attempts to
build the c++ libraries using gcc with the supplied CFLAGS and then dies
because "-ieee" is not a valid gcc argument. Trying STAGE1_CFLAGS didn't
seem to do the right thing either, and I didn't have any other decent
guesses. :-)

Is it possible to teach configure that -ieee is needed when using the native
Tru64 cc compiler? (Well, "needed" for 5.1 and, it appears, "harmless" for
earlier versions.)

I have a couple more observations that I will open separate reports on.

Cheers,

	Scott


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16787


  parent reply	other threads:[~2004-07-30 14:54 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 [this message]
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
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=20040730145408.2611.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: 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).