public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug java/12759] New: BInary compatibility: rip out -fno-assume-compiled
@ 2003-10-24 13:41 aph at gcc dot gnu dot org
  2003-10-24 16:48 ` [Bug java/12759] " pinskia at gcc dot gnu dot org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: aph at gcc dot gnu dot org @ 2003-10-24 13:41 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: BInary compatibility: rip out -fno-assume-compiled
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: aph at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 BugsThisDependsOn: 12725

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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug java/12759] BInary compatibility: rip out -fno-assume-compiled
  2003-10-24 13:41 [Bug java/12759] New: BInary compatibility: rip out -fno-assume-compiled aph at gcc dot gnu dot org
@ 2003-10-24 16:48 ` pinskia at gcc dot gnu dot org
  2003-10-24 19:09 ` tromey at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2003-10-24 16:48 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2003-10-24 16:48:18
               date|                            |


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug java/12759] BInary compatibility: rip out -fno-assume-compiled
  2003-10-24 13:41 [Bug java/12759] New: BInary compatibility: rip out -fno-assume-compiled aph at gcc dot gnu dot org
  2003-10-24 16:48 ` [Bug java/12759] " pinskia at gcc dot gnu dot org
@ 2003-10-24 19:09 ` tromey at gcc dot gnu dot org
  2003-10-25  3:48 ` bryce at mckinlay dot net dot nz
  2004-10-20 16:02 ` [Bug java/12759] Binary " aph at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: tromey at gcc dot gnu dot org @ 2003-10-24 19:09 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From tromey at gcc dot gnu dot org  2003-10-24 19:09 -------
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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug java/12759] BInary compatibility: rip out -fno-assume-compiled
  2003-10-24 13:41 [Bug java/12759] New: BInary compatibility: rip out -fno-assume-compiled aph at gcc dot gnu dot org
  2003-10-24 16:48 ` [Bug java/12759] " pinskia at gcc dot gnu dot org
  2003-10-24 19:09 ` tromey at gcc dot gnu dot org
@ 2003-10-25  3:48 ` bryce at mckinlay dot net dot nz
  2004-10-20 16:02 ` [Bug java/12759] Binary " aph at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: bryce at mckinlay dot net dot nz @ 2003-10-25  3:48 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From bryce at mckinlay dot net dot nz  2003-10-25 03:40 -------
I was thinking the same thing. We could perhaps think of a better name for it

-fassume-local ?
-fassume-same-binary ?


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug java/12759] Binary compatibility: rip out -fno-assume-compiled
  2003-10-24 13:41 [Bug java/12759] New: BInary compatibility: rip out -fno-assume-compiled aph at gcc dot gnu dot org
                   ` (2 preceding siblings ...)
  2003-10-25  3:48 ` bryce at mckinlay dot net dot nz
@ 2004-10-20 16:02 ` aph at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: aph at gcc dot gnu dot org @ 2004-10-20 16:02 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From aph at gcc dot gnu dot org  2004-10-20 16:02 -------
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.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor
   Last reconfirmed|2004-08-09 02:01:07         |2004-10-20 16:02:51
               date|                            |


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-10-20 16:02 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-24 13:41 [Bug java/12759] New: BInary compatibility: rip out -fno-assume-compiled aph at gcc dot gnu dot org
2003-10-24 16:48 ` [Bug java/12759] " pinskia at gcc dot gnu dot org
2003-10-24 19:09 ` tromey at gcc dot gnu dot org
2003-10-25  3:48 ` bryce at mckinlay dot net dot nz
2004-10-20 16:02 ` [Bug java/12759] Binary " aph at gcc dot gnu dot org

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).