public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/12527] [3.4 regression] [arm] bootstrap error on arm-linux, miscompiling genconstants
Date: Wed, 15 Oct 2003 14:30:00 -0000 [thread overview]
Message-ID: <20031015143047.10195.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031006200259.12527.debian-gcc@lists.debian.org>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12527
rearnsha at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Last reconfirmed|2003-10-14 04:10:30 |2003-10-15 14:30:46
date| |
------- Additional Comments From rearnsha at gcc dot gnu dot org 2003-10-15 14:30 -------
I've just realized what is going wrong here. It's because the arm-linux target
is (erroneously in my opinion) including arm/unknown-elf.h. This file defaults
the CPU target to ARM7TDMI, which means that the bx instruction becomes
available. The patch in question just means that this latent bug has gone critical.
You can probably work around this problem for now by configuring with
--with-cpu=arm6 or some other suitable CPU.
next prev parent reply other threads:[~2003-10-15 14:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 20:03 [Bug target/12527] New: [3.4 regression] [arm] bootstrap error on arm-linux debian-gcc at lists dot debian dot org
2003-10-09 1:43 ` [Bug target/12527] " pinskia at gcc dot gnu dot org
2003-10-11 3:32 ` [Bug target/12527] [3.4 regression] [arm] bootstrap error on arm-linux, miscompiling genconstants pinskia at gcc dot gnu dot org
2003-10-11 11:34 ` doko at cs dot tu-berlin dot de
2003-10-11 12:06 ` rearnsha at gcc dot gnu dot org
2003-10-12 7:24 ` doko at cs dot tu-berlin dot de
2003-10-13 12:41 ` rearnsha at gcc dot gnu dot org
2003-10-13 20:56 ` doko at cs dot tu-berlin dot de
2003-10-14 4:10 ` pinskia at gcc dot gnu dot org
2003-10-14 6:51 ` doko at cs dot tu-berlin dot de
2003-10-14 9:52 ` rearnsha at gcc dot gnu dot org
2003-10-14 20:49 ` debian-gcc at lists dot debian dot org
2003-10-15 13:30 ` rearnsha at gcc dot gnu dot org
2003-10-15 14:30 ` rearnsha at gcc dot gnu dot org [this message]
2003-12-21 3:28 ` steven at gcc dot gnu dot org
2004-01-10 22:49 ` pinskia at gcc dot gnu dot org
2004-01-12 16:12 ` [Bug bootstrap/12527] " rearnsha at gcc dot gnu dot org
2004-01-12 16:18 ` pinskia at gcc dot gnu dot org
2004-01-12 17:05 ` bangerth at dealii dot org
2004-01-14 9:18 ` steven at gcc dot gnu dot org
2004-01-14 9:26 ` rearnsha at arm dot com
2004-01-14 17:51 ` cvs-commit at gcc dot gnu dot org
2004-01-14 17:56 ` rearnsha at gcc dot gnu dot org
2004-01-27 13:08 ` cvs-commit at gcc dot gnu dot org
2004-03-30 20:44 ` cvs-commit at gcc dot gnu dot org
2004-03-30 21:17 ` [Bug bootstrap/12527] [3.3/3.4 " pinskia at gcc dot gnu dot org
2005-08-14 18:53 ` buytenh at wantstofly dot org
2005-08-15 9:37 ` rearnsha 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=20031015143047.10195.qmail@sources.redhat.com \
--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).