Another solution might be for the compiler to generate restrict (or _RESTRICT) and put an appropriate define in whirl2c.h to control it).
Murthy From: Li Shengmei [mailto:[email protected]] Sent: Tuesday, August 17, 2010 3:03 AM To: [email protected] Subject: [Open64-devel] About genarating C codes while doing whirl2c? Hi, all Is there any way to prevent open64 from generating C extensions while doing whirl2c? I input standard C codes and want to obtain standard C codes after whirl2c. Sometime it may generate keyword like "restrict" after whirl2c which some compiler can't recognize. Thanks. May ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Open64-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/open64-devel ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Open64-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/open64-devel
