public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17209] New: ld-collate.s: Error: bad immediate value for offset (4096) Date: Fri, 27 Aug 2004 08:10:00 -0000 [thread overview] Message-ID: <20040827081022.17209.dank@kegel.com> (raw) Building glibc's locale/programs/ld-collate.c causes failures with some arm targets. The errors seem to be in the last function, which is 1200 lines long. Exactly which ones depends a bit on exactly what version you're building. This happens with several versions of glibc (2.2.5, 2.3.3-20040822) and with several variants of CPU type (e.g. even plain arm supposedly may trigger it; see http://www.handhelds.org/hypermail/kernel-discuss/0/0066.html) It happened with gcc-3.4.0 (see http://www.kegel.com/crosstool/crosstool-0.28-rc26/buildlogs/0.28/arm-softfloat-gcc-3.4.0-glibc-2.2.5.txt) and again with gcc-3.4.1. I'll attach a preprocessed input file. -- Summary: ld-collate.s: Error: bad immediate value for offset (4096) Product: gcc Version: 3.4.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dank at kegel dot com CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: arm-xscale-linux-gnu, other arm variants http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17209
next reply other threads:[~2004-08-27 8:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-27 8:10 dank at kegel dot com [this message] 2004-08-27 8:11 ` [Bug target/17209] " dank at kegel dot com 2004-08-31 5:41 ` dank at kegel dot com 2004-10-06 0:20 ` rearnsha at gcc dot gnu dot org 2004-10-06 6:41 ` dank at kegel dot com 2004-10-06 6:46 ` dank at kegel dot com 2005-01-31 15:58 ` 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=20040827081022.17209.dank@kegel.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: 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).