Bug 12759 - Binary compatibility: rip out -fno-assume-compiled
Summary: Binary compatibility: rip out -fno-assume-compiled
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: java (show other bugs)
Version: unknown
: P2 minor
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on: 12725
Blocks:
  Show dependency tree / graph
 
Reported: 2003-10-24 13:39 UTC by Andrew Haley
Modified: 2016-09-30 22:50 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-07-20 00:29:53

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 Andrew Haley 2003-10-24 13:39:48 UTC 
no-assume-compiled is undocumented and probably broken, but some software,
particularly Eclipse, relies on it.  When indirect-dispatch works well enough for
Eclipse we should rip out no-assume-compiled.
Comment 1 Tom Tromey 2003-10-24 19:09:03 UTC 
I wonder if we should instead keep the no-assume-compiled
command-line processing, and reuse it to decide when
to generate more tightly bound code and when to generate
indirect-dispatch code.

The internal "no-assume-compiled ABI" should definitely be
removed.
Comment 2 Bryce McKinlay 2003-10-25 03:40:29 UTC 
I was thinking the same thing. We could perhaps think of a better name for it

-fassume-local ?
-fassume-same-binary ?
Comment 3 Andrew Haley 2004-10-20 16:02:50 UTC 
This is fairly low priority because it doesn't really affect anything.

However, removing no-assume-compiled could cause considerable lossage.

For the time being, we could simply remove the command line option.
Comment 4 Andrew Pinski 2016-09-30 22:50:06 UTC 
Closing as won't fix as the Java front-end has been removed from the trunk.