From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Mark Klein Cc: egcs@egcs.cygnus.com, java-discuss@sourceware.cygnus.com Subject: Re: assemble_external on .class files Date: Sat, 22 May 1999 14:23:00 -0000 Message-id: <6642.927407954@upchuck.cygnus.com> References: <4.1.19990520204749.00c7fa90@garfield.dis.com> X-SW-Source: 1999-05/msg00632.html In message < 4.1.19990520204749.00c7fa90@garfield.dis.com >you write: > External procedure labels need to be .IMPORTED before they can > be used on my platform. Some of these are part of a dispatch table > created from classes such as java::lang::Object. My first attempt at > resolving this was to place an assemble_external() in layout_class(), > but that results in a lot of clutter with .IMPORT statements for a > whole bunch of things that really are not referenced. I suppose this > could be my brute force method, but I would prefer to only do the > .IMPORT for referenced methods/classes. I wouldn't worry about the extra .IMPORTs. In fact, it's a little known aspect of SOM that the assembler is responsible for _not_ adding an imported symbol to the undefined symbols for a module if that symbol is not actually referenced. Jeff From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Mark Klein Cc: egcs@egcs.cygnus.com, java-discuss@sourceware.cygnus.com Subject: Re: assemble_external on .class files Date: Mon, 31 May 1999 21:36:00 -0000 Message-ID: <6642.927407954@upchuck.cygnus.com> References: <4.1.19990520204749.00c7fa90@garfield.dis.com> X-SW-Source: 1999-05n/msg00633.html Message-ID: <19990531213600.YuwPEJvbcvrkGdP4tVWcnv0ulyohkW48tcxC7O4BbG0@z> In message < 4.1.19990520204749.00c7fa90@garfield.dis.com >you write: > External procedure labels need to be .IMPORTED before they can > be used on my platform. Some of these are part of a dispatch table > created from classes such as java::lang::Object. My first attempt at > resolving this was to place an assemble_external() in layout_class(), > but that results in a lot of clutter with .IMPORT statements for a > whole bunch of things that really are not referenced. I suppose this > could be my brute force method, but I would prefer to only do the > .IMPORT for referenced methods/classes. I wouldn't worry about the extra .IMPORTs. In fact, it's a little known aspect of SOM that the assembler is responsible for _not_ adding an imported symbol to the undefined symbols for a module if that symbol is not actually referenced. Jeff