public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Wed, 22 Sep 2010 08:07:00 -0000	[thread overview]
Message-ID: <20100922080746.4002.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44095-7665@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jakub at gcc dot gnu dot org  2010-09-22 08:07 -------
That semantics can't cope well with -fcompare-debug though, where cc1 etc. is
invoked multiple times.  If you remove some options forever, they wouldn't
appear on the next cc1 etc. invocation line and thus that would behave
differently.  I wonder if e.g. not using %(invoke_as) but instead duplicating
its text in java/jvspec.c with additional %<findirect-dispatch right after as
and before %(asm_options) wouldn't do the trick.
Or we need a different % letter that would have the previous behavior, though
am not sure if it could ever work with gcj -fcompare-debug -fmain=myclass
myclass.java


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44095


  parent reply	other threads:[~2010-09-22  8:07 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
2010-09-22  6:06 ` ebotcazou at gcc dot gnu dot org
2010-09-22  8:07 ` jakub at gcc dot gnu dot org [this message]
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=20100922080746.4002.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: 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).