public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/19601] [4.0 Regression] make bootstrap-lean fails: insn-conditions.c:189: error: `flag_unsafe_math_optimizations' undeclared
Date: Mon, 24 Jan 2005 07:53:00 -0000 [thread overview]
Message-ID: <20050124075308.1334.qmail@sourceware.org> (raw)
In-Reply-To: <20050124071452.19601.olh@suse.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-24 07:53 -------
Hmm, interesting.
'flag_unsafe_math_optimizations' should be defined in options.h which is built each time. Can you
attach the full log? I am going to try this myself to see if something goes wrong here.
I see that you are using -j12, maybe there is dependancies problem.
And it really does look that way:
bootstrap-lean : clean_s1 clean_s2 stage3_build
--
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Summary|make bootstrap-lean fails: |[4.0 Regression] make
|insn-conditions.c:189: |bootstrap-lean fails: insn-
|error: |conditions.c:189: error:
|`flag_unsafe_math_optimizati|`flag_unsafe_math_optimizati
|ons' undeclared |ons' undeclared
Target Milestone|--- |4.0.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19601
next prev parent reply other threads:[~2005-01-24 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 7:15 [Bug bootstrap/19601] New: " olh at suse dot de
2005-01-24 7:53 ` pinskia at gcc dot gnu dot org [this message]
2005-01-24 9:01 ` [Bug bootstrap/19601] [4.0 Regression] " olh at suse dot de
2005-01-24 13:50 ` pinskia at gcc dot gnu dot org
2005-01-27 0:15 ` rth at gcc dot gnu dot org
2005-01-27 7:51 ` olh at suse dot de
2005-01-30 14:34 ` olh at suse dot de
2005-01-30 15:22 ` olh at suse dot de
2005-04-21 12:54 ` 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=20050124075308.1334.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).