Does anyone know how to use whirl2c/whirl2f to convert .B/.I files?
I have tried that, but the result is like this: (errors are the same with
-TARG:abi=32/64, or whirl2c_be)
$ ./whirl2c ~/test/main.B
"/home/open64/test/main.c": Error: Invalid format revision (abi of whirl
file doesn't match abi fr
For control on generating the .I files from IPA, you can look at
ipa/common/ipc_bwrite.cxx (start from IP_WRITE_pu()). Basically by default, it
starts emitting PUs into a .I file, until the file size exceeds a predefined
limit, then it moves on to the next .I file.
If you are looking for matchi
Author: sje
Date: 2010-07-06 19:03:20 -0400 (Tue, 06 Jul 2010)
New Revision: 3269
Modified:
trunk/osprey/common/ipfec_targ_info/gen/itanium_gen.cxx
Log:
Add extra argument to EKAPI_MapResource call so that the varargs does not
try to access more arguments then are passed.
Approved by: Roy Ju
you can also use whirl2c, whirl2f... to convert the .I files back to
.c/c++/f files for easier reading and debugging.
Sun
On Tue, Jul 6, 2010 at 4:51 PM, Tianwei wrote:
>
>
> On Tue, Jul 6, 2010 at 4:17 PM, Li Shengmei wrote:
>
>> Hi,all
>>I want to know how the .I files which are gene
On Tue, Jul 6, 2010 at 4:17 PM, Li Shengmei wrote:
> Hi,all
>I want to know how the .I files which are generated during IPA. The
> debug document of IPA is "TBD" in the doc of Open64.
>Does anyone know the generation of .I files or give some suggestions
> about studying it?
>
are you interested in a different compilation model for IPA? I.e. say,
matching .I file for each .c input file? What is the purpose of your
studying the .I files?
The original purpose is to enable parallel compilation by the later backend
phases. I believe partitioning of the call graph to maximize
Hi,all
I want to know how the .I files which are generated during IPA. The
debug document of IPA is "TBD" in the doc of Open64.
Does anyone know the generation of .I files or give some suggestions
about studying it?
What is the principle of generating .I files? How can I con
