public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com> To: davem@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/6383: boehm-gc busted on all sparc64 targets Date: Mon, 22 Apr 2002 08:46:00 -0000 [thread overview] Message-ID: <20020422154604.18147.qmail@sources.redhat.com> (raw) The following reply was made to PR target/6383; it has been noted by GNATS. From: Jeff Sturm <jsturm@one-point.com> To: "David S. Miller" <davem@redhat.com> Cc: gcc-gnats@gcc.gnu.org, rth@redhat.com, tromey@redhat.com, gcc-bugs@gcc.gnu.org Subject: Re: target/6383: boehm-gc busted on all sparc64 targets Date: Mon, 22 Apr 2002 11:40:35 -0400 (EDT) On Sun, 21 Apr 2002, David S. Miller wrote: > Thanks for tracking this down and testing your fix Jeff. I suspected > that lack of DYNAMIC_LOADING for solaris sparc64 was bogus and I > had noted it to tromey the other evening. I checked that the solaris breakage is from the last gc import. I'm not too keen about blindly importing each new release for this sort of reason. I don't have a better suggestion though, except making gcc the official repository for boehm-gc, as had been discussed at one time. ISTR there was another (java?) PR related to this one. I haven't tried a full testsuite, but at least simple Java programs are now running for me on sparc64. Thanks for taking care of this. Jeff
next reply other threads:[~2002-04-22 15:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-22 8:46 Jeff Sturm [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-21 23:12 davem 2002-04-21 23:06 David S. Miller 2002-04-21 21:46 Jeff Sturm 2002-04-21 4:00 davem 2002-04-19 21:40 davem 2002-04-19 21:16 davem
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=20020422154604.18147.qmail@sources.redhat.com \ --to=jsturm@one-point.com \ --cc=davem@gcc.gnu.org \ --cc=gcc-prs@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).