Bug 7739 - compile with -findirect-dispatch by default
Summary: compile with -findirect-dispatch by default
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: java (show other bugs)
Version: 3.4.0
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: ABI
Depends on:
Blocks:
 
Reported: 2002-08-27 14:26 UTC by Jeff Sturm
Modified: 2016-09-30 22:50 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-09-30 05:25:09

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Sturm 2002-08-27 14:26:01 UTC 
Consider turning -findirect-dispatch on by default.  It solves some serious problems with compatibility of classes, e.g. adding/removing methods or changing method order.

The obvious drawback is decreased performance.  However some studies have shown the impact to be minimal, and -fno-indirect-dispatch can get the old behavior.

Release:
3.4?
Comment 1 Dara Hazeghi 2003-06-08 17:06:45 UTC 
Jeff, what's the status of this? Do you have a testcase exhibiting the problematic behavior? Thanks,

Dara
Comment 2 Andrew Pinski 2003-07-24 11:52:27 UTC 
still true (-findirect-dispatch is enabled by default) on the mainline (20030724).
Comment 3 Nathanael C. Nerode 2003-08-03 17:40:03 UTC 
>still true (-findirect-dispatch is enabled by default) on the mainline
>(20030724).

Waaaait.  This bug is that -findirect-dispatch was *off* by default and should
have been *on*.  If -findirect-dispatch is enabled by default in the mainline,
then the bug is *fixed*.

Andrew?  Could you clarify?  Did you get confused about the nature of the bug,
or did you accidentally omit the word 'not'?
Comment 4 Andrew Pinski 2003-08-03 17:42:23 UTC 
I missed the word not. woops.
Comment 5 Andrew Pinski 2016-09-30 22:50:35 UTC 
Closing as won't fix as the Java front-end has been removed from the trunk.