Earlier this year, I proposed making a change so that targ_info uses statically-linked scheduling info. In preparation for making that change, I need to fork a few files, creating separate copies in ipfec_targ_info (used only for IA-64).
Some background: it appears that much of targ_info was forked to create ipfec_targ_info long ago. In ipfec_targ_info, some files from the "old" targ_info are used, including ti_init.[ch] (TI_Initialize) and ti_si[_types].h (SI interface). Using statically-linked scheduling info will require changes to these files: TI_Initialize will no longer call load_so and the references to the generated data in ti_si.h will change. Because I don't have the ability to fully build and test the IA-64 port and it has diverged so much in this area, my intention is to leave it as-is for now; it will continue to use scheduling info packaged in DSO's. After this change, modifications to ti_init.[ch] and ti_si[_types].h in osprey/common/targ_info will not affect IA-64. The details of the change are in the attached msg.txt file. In addition to the changes shown in the diff file, the patch also copies the following files from osprey/common/targ_info/access to osprey/common/ipfec_targ_info/access: ti_init.c, ti_init.h, ti_si.h, ti_si_types.h Could a gatekeeper please review the patch? Thanks, -David Coakley / AMD Open Source Compiler Engineering
Create fork of targ_info SI-related files for ipfec_targ_info. After this change, the targ_info scheduling info (SI) interface can be changed separately for targ_info and ipfec_targ_info. o Make ipfec_targ_info-specific copies of ti_init.[ch], ti_si[_types].h. o When building the backend (be), reference targ_info source files through the configurable variable TARG_INFO_NAME. o When building ipfec_targ_info, make references to source files in osprey/common/targ_info through explicit soft links rather than using VPATH. Compiling this way allows header files in ipfec_targ_info to take precedence over those with the same name in targ_info, and makes it more clear which source files from targ_info are being shared. o Delete mistaken svn:executable property from source files in osprey/common/targ_info/access.
ipfec_fork.diff
Description: Binary data
------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
