public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edmar at freescale dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26459] New: gcc-4.1.0 RC2 fails to build on certain PowerPC targets
Date: Fri, 24 Feb 2006 18:42:00 -0000 [thread overview]
Message-ID: <bug-26459-12262@http.gcc.gnu.org/bugzilla/> (raw)
When configuring gcc with:
--target=powerpc-unknown-linux-gnuspe --host=powerpc-unknown-linux-gnuspe
--enable-e500_double
this file will be included:
gcc/config/rs6000/e500-double.h
which in turn uses the variable
rs6000_float_gprs_string
which is not defined anywhere. (So the build stops with undefined sysmbol
error)
This problem can be detected as far as 20060206.
Gcc 4.0.2 builds fine with the same configuration options.
--
Summary: gcc-4.1.0 RC2 fails to build on certain PowerPC targets
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: edmar at freescale dot com
GCC build triplet: powerpc-unknown-linux-gnuspe
GCC host triplet: powerpc-unknown-linux-gnuspe
GCC target triplet: powerpc-unknown-linux-gnuspe
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26459
next reply other threads:[~2006-02-24 18:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 18:42 edmar at freescale dot com [this message]
2006-02-24 18:43 ` [Bug target/26459] [4.1/4.2 Regression] gcc-4.1.0 RC2 fails to build on powerpc e500-double targets pinskia at gcc dot gnu dot org
2006-02-24 18:45 ` [Bug target/26459] [4.1/4.2 Regression] gcc " pinskia at gcc dot gnu dot org
2006-02-24 18:54 ` edmar at freescale dot com
2006-02-24 19:10 ` mmitchel at gcc dot gnu dot org
2006-02-24 19:13 ` edmar at freescale dot com
2006-02-24 19:29 ` mark at codesourcery dot com
2006-02-24 20:48 ` edmar at freescale dot com
2006-02-24 21:14 ` mark at codesourcery dot com
2006-02-24 21:17 ` edmar at freescale dot com
2006-02-24 22:03 ` mmitchel at gcc dot gnu dot org
2006-02-27 21:42 ` steven at gcc dot gnu dot org
2006-02-27 22:42 ` steven at gcc dot gnu dot org
2006-02-27 22:43 ` steven at gcc dot gnu dot org
2006-02-27 22:53 ` steven at gcc dot gnu dot org
2006-02-28 20:35 ` mmitchel at gcc dot gnu dot org
2006-03-24 14:23 ` amodra at bigpond dot net dot au
2006-03-25 2:59 ` amodra at bigpond dot net dot au
2006-03-25 3:01 ` amodra at bigpond dot net dot au
2006-03-26 22:48 ` amodra at gcc dot gnu dot org
2006-03-26 22:49 ` amodra at gcc dot gnu dot org
2006-03-27 1:41 ` amodra at bigpond dot net dot au
2006-03-27 4:36 ` patchapp at dberlin dot org
2006-03-31 1:25 ` amodra at gcc dot gnu dot org
2006-03-31 1:27 ` amodra at gcc dot gnu dot org
2006-03-31 1:54 ` amodra at bigpond dot net dot au
2006-04-10 15:42 ` edmar at freescale dot com
2006-04-11 0:33 ` amodra at gcc dot gnu dot org
2006-04-11 0:36 ` amodra at gcc dot gnu dot org
2006-04-11 0:37 ` amodra at bigpond dot net dot au
2006-04-12 15:36 ` edmar at freescale dot com
2006-04-13 5:10 ` amodra at gcc dot gnu dot org
2006-04-13 5:46 ` amodra at gcc dot gnu dot org
2006-04-16 18:39 ` mmitchel at gcc dot gnu dot org
2006-04-17 0:09 ` amodra at bigpond dot net dot au
2006-04-17 15:22 ` edmar at freescale dot com
2006-04-17 15:37 ` mark at codesourcery dot com
2006-04-17 15:44 ` edmar at freescale dot com
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=bug-26459-12262@http.gcc.gnu.org/bugzilla/ \
--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).