public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/52805] [4.8 Regression] 243 new GCC HEAD@185977 regressions (libjava failures)
Date: Sun, 01 Apr 2012 17:29:00 -0000 [thread overview]
Message-ID: <bug-52805-8172-3bWIkZn0It@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52805-8172@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52805
--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> 2012-04-01 17:28:47 UTC ---
I suspect you might have altered the priority of class discovery methods
inadvertently.
e.g. AFAICT, although darwin defines JCR_SECTION_NAME, there is no crt
machinery to deal with it [darwin has it's own crt code] - it's on my TODO to
look at that & confirm/deny/fix as appropriate.
not sure why i686-pc-linux is failing tho (since crtstuff does seem to have
provision for JCR - but not checked in any depth).
Darwin folks might like to try:
Index: gcc/config/darwin.h
===================================================================
--- gcc/config/darwin.h (revision 186018)
+++ gcc/config/darwin.h (working copy)
@@ -847,6 +847,7 @@ enum machopic_addr_class {
/* Java runtime class list. */
#define JCR_SECTION_NAME "__DATA,jcr,regular,no_dead_strip"
+#define TARGET_USE_JCR_SECTION 0
#undef ASM_PREFERRED_EH_DATA_FORMAT
#define ASM_PREFERRED_EH_DATA_FORMAT(CODE,GLOBAL) \
next prev parent reply other threads:[~2012-04-01 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 11:34 [Bug java/52805] New: " dominiq at lps dot ens.fr
2012-03-31 20:10 ` [Bug java/52805] " iains at gcc dot gnu.org
2012-04-01 17:29 ` iains at gcc dot gnu.org [this message]
2012-04-01 22:31 ` dominiq at lps dot ens.fr
2012-04-02 9:15 ` rguenth at gcc dot gnu.org
2012-04-02 16:30 ` iains at gcc dot gnu.org
2012-04-02 17:13 ` iains at gcc dot gnu.org
2012-04-03 9:04 ` dominiq at lps dot ens.fr
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=bug-52805-8172-3bWIkZn0It@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-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: 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).