public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmathew at gcc dot gnu dot org" <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: Fri, 02 Sep 2005 09:42:00 -0000 [thread overview]
Message-ID: <20050902094155.9455.qmail@sourceware.org> (raw)
In-Reply-To: <20050831205412.23662.ngmlinux@gmail.com>
------- Additional Comments From rmathew at gcc dot gnu dot org 2005-09-02 09:41 -------
(In reply to comment #10)
> (In reply to comment #9)
> > I think it is the same problem with Boehm-GC on ARM/Linux that
> > has been solved in upstream sources.
>
> Has this fix been officially submited to gcc for inclusion in 4.0.X?
We import the Boehm-GC from time to time into mainline CVS (GCC) from
upstream sources. I think upstream sources already have this patch applied.
It is unlikely that the 4.0.x series will pick up an updated Boehm-GC,
though mainline can (although it is a bit too close to the 4.1 freeze).
In the interim, you can see if this resolves your issue and get by with
a local patch.
> Are any fixes required on the target itself (ie. in it's libraries) or just on
> the arm-linux-gcj cross compiler source?
Sorry, I don't know the answer to this as I work on x86-linux only. But from
perusing the related messages, it does not look like any other change is
needed, but I might be mistaken.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23662
next prev parent reply other threads:[~2005-09-02 9:42 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 [this message]
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
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=20050902094155.9455.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).