public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/44095] [4.5/4.6 Regression] massive java failures due to -findirect-dispatch breakage on sparc64-linux Date: Tue, 21 Sep 2010 21:45:00 -0000 [thread overview] Message-ID: <20100921214522.13141.qmail@sourceware.org> (raw) In-Reply-To: <bug-44095-7665@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from ebotcazou at gcc dot gnu dot org 2010-09-21 21:45 ------- > Java is severely broken on sparc64-linux with gcc 4.5/4.6, which is a major > regression from 4.4: > > http://gcc.gnu.org/ml/gcc-testresults/2010-05/msg00853.html (4.6 broken) > http://gcc.gnu.org/ml/gcc-testresults/2010-05/msg00681.html (4.5 broken) > http://gcc.gnu.org/ml/gcc-testresults/2010-05/msg00472.html (4.4 works) > > The detailed test suite logs show that _every_ -findirect-dispatch test case > SEGFAULTs shortly after startup. > > I've bisected trunk and identified r155622 as the cause: > > Author: jakub > Date: Mon Jan 4 16:02:41 2010 > New Revision: 155622 > > URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155622 > Log: > PR driver/42442 > * gcc.c (SWITCH_IGNORE_PERMANENTLY): Define. > (do_self_spec): For switches with SWITCH_IGNORE set set also > SWITCH_IGNORE_PERMANENTLY. > (check_live_switch): Check SWITCH_IGNORE_PERMANENTLY instead > of SWITCH_IGNORE. > > [...] > > The main difference is that in the working compiler, the java classes are > assembled with -K PIC but the generated main() is not, while in the broken > compiler both the java classes and the generated main() are assembled with -K > PIC. Thanks for the detailed analysis. > I note that gcc/java/jvspec.c has %<findirect-dispatch, and that PR42442 is > about correcting the handling of %<match=native. Clearly something here > doesn't mix well. My interpretation is that the %<findirect-dispatch for cc1 used to cancel the effect of -findirect-dispatch for subsequent programs invoked by the driver, in particular 'as' in this case. Jakub's change disables this cancellation so -findirect-dispatch is passed to 'as' and thus the kludge I put in ASM_SPEC for Linux triggers, which breaks because cc1 hasn't compiled the file in PIC mode. -- ebotcazou at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2010-09-20 21:40:00 |2010-09-21 21:45:21 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44095
next prev parent reply other threads:[~2010-09-21 21:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-12 11:00 [Bug java/44095] New: [4.5/4.6 regression] " mikpe at it dot uu dot se 2010-05-12 11:35 ` [Bug java/44095] " rguenth at gcc dot gnu dot org 2010-05-19 12:59 ` [Bug java/44095] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org 2010-07-31 9:33 ` rguenth at gcc dot gnu dot org 2010-09-20 21:40 ` ebotcazou at gcc dot gnu dot org 2010-09-21 21:45 ` ebotcazou at gcc dot gnu dot org [this message] 2010-09-22 6:06 ` ebotcazou at gcc dot gnu dot org 2010-09-22 8:07 ` jakub at gcc dot gnu dot org 2010-09-22 21:15 ` ebotcazou at gcc dot gnu dot org 2010-09-22 21:17 ` ebotcazou at gcc dot gnu dot org 2010-09-22 21:19 ` ebotcazou 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=20100921214522.13141.qmail@sourceware.org \ --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: 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).