public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ngmlinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug boehm-gc/23662] Binaries generated by arm-linux-gcj segfault on execution on arm target
Date: Sun, 04 Sep 2005 03:25:00 -0000 [thread overview]
Message-ID: <20050904032523.30949.qmail@sourceware.org> (raw)
In-Reply-To: <20050831205412.23662.ngmlinux@gmail.com>
------- Additional Comments From ngmlinux at gmail dot com 2005-09-04 03:25 -------
Ok after recompiling the static HelloWorld.exe with the patched toolchain the
following happens upon execution on the target:
===code==========================================================================
[root@ARMCore test]$ ./HelloWorld.exe
HelloWorld.exe: dl-runtime.c:72: fixup: Assertion `((reloc->r_info) & 0xff) ==
22' failed.
Aborted
=================================================================================
The following post although refering to a dated toolchain appears as though it
may be relevant:
http://www.mail-archive.com/linux-arm@lists.arm.linux.org.uk/msg03071.html
Does this seem to be on the right track?
I'm noticing that in general, very few bugs if any in the arm-linux port of gcc
have been fixed since the gcc-2.x.x and gcc-3.x.x toolchain releases.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23662
next prev parent reply other threads:[~2005-09-04 3:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 20:59 [Bug java/23662] New: " ngmlinux at gmail dot com
2005-08-31 21:03 ` [Bug java/23662] " ngmlinux at gmail dot com
2005-08-31 21:04 ` [Bug boehm-gc/23662] " pinskia at gcc dot gnu dot org
2005-08-31 21:10 ` pinskia at gcc dot gnu dot org
2005-08-31 21:21 ` pinskia at gcc dot gnu dot org
2005-09-01 0:57 ` ngmlinux at gmail dot com
2005-09-01 1:02 ` ngmlinux at gmail dot com
2005-09-01 1:04 ` ngmlinux at gmail dot com
2005-09-01 1:08 ` pinskia at gcc dot gnu dot org
2005-09-01 1:40 ` ngmlinux at gmail dot com
2005-09-01 9:36 ` rmathew at gcc dot gnu dot org
2005-09-01 19:46 ` ngmlinux at gmail dot com
2005-09-02 9:42 ` rmathew at gcc dot gnu dot org
2005-09-02 17:16 ` tromey at gcc dot gnu dot org
2005-09-04 0:14 ` ngmlinux at gmail dot com
2005-09-04 2:35 ` ngmlinux at gmail dot com
2005-09-04 3:25 ` ngmlinux at gmail dot com [this message]
2005-09-04 4:07 ` Andrew Pinski
2005-09-04 3:52 ` ngmlinux at gmail dot com
2005-09-04 4:07 ` pinskia at physics dot uc dot edu
2005-09-04 4:20 ` ngmlinux at gmail dot com
2005-09-04 4:22 ` pinskia at gcc dot gnu dot org
2005-09-04 5:03 ` ngmlinux at gmail dot com
2005-09-06 14:21 ` cvs-commit at gcc dot gnu dot org
2005-09-06 14:22 ` cvs-commit at gcc dot gnu dot org
2005-09-06 14:23 ` tromey at gcc dot gnu dot org
2005-09-07 14:07 ` 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=20050904032523.30949.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).