- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks,
Aniruddha
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, one can always be sure that a macro is expanded. Why not use the inline code as a macro. If it is possible to get away with using just macros without inline assembly, it may even be further optimized by the compiler on a separate pass, while extern inline code may not. Even try both using macros and extern inline functions and see which one is faster, if time is permitted. Also, for portability if the code is good enough that other people may want to use it, just stick with C++ code and macros so that it can be compiled and used on other architectures as well. If one is an expert assembly writer, they would have enough code to want to make an inline assembly function call. And if the code being used is making the extern inline call, isnt the routine already compiled, and would not be expanded. Then again obviously I see your problem. I do not know the proper optimization levels to use to get these function calls to be used as extern inline expanded code. Interesting problem,
Ryan Mauldin
Message Edited by rmauldin on 10-17-2005 02:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page