search for: vdef

...fndef _PARAVIRTUAL_INTERFACE_H_ +#define _PARAVIRTUAL_INTERFACE_H_ + +#include "vmiCalls.h" + +/* + *--------------------------------------------------------------------- + * + * VMI Option ROM API + * + *--------------------------------------------------------------------- + */ +#define VDEF(call) VMI_CALL_##call, +typedef enum VMICall { + VMI_CALLS + NUM_VMI_CALLS +} VMICall; +#undef VDEF + +#define VMI_SIGNATURE 0x696d5663 /* "cVmi" */ + +#define VMI_API_REV_MAJOR 13 +#define VMI_API_REV_MINOR 0 + +/* Flags used by VMI_Reboot call */ +#define VMI_REB...

...fndef _PARAVIRTUAL_INTERFACE_H_ +#define _PARAVIRTUAL_INTERFACE_H_ + +#include "vmiCalls.h" + +/* + *--------------------------------------------------------------------- + * + * VMI Option ROM API + * + *--------------------------------------------------------------------- + */ +#define VDEF(call) VMI_CALL_##call, +typedef enum VMICall { + VMI_CALLS + NUM_VMI_CALLS +} VMICall; +#undef VDEF + +#define VMI_SIGNATURE 0x696d5663 /* "cVmi" */ + +#define VMI_API_REV_MAJOR 13 +#define VMI_API_REV_MINOR 0 + +/* Flags used by VMI_Reboot call */ +#define VMI_REB...

Hi, I see that there are two functions in your code that are O(n^2) in number of instructions of the program: getCandidatePairs and buildDepMap. I think that you could make these two functions faster if you work on some form of factored def-use chains for memory, like the VUSE/VDEFs of GCC. I was trying to find a similar representation in LLVM: isn't there already a virtual SSA representation for memory references in LLVM? Thanks, Sebastian -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum

...> I see that there are two functions in your code that are O(n^2) in > number of instructions of the program: getCandidatePairs and > buildDepMap. I think that you could make these two functions faster > if you work on some form of factored def-use chains for memory, like > the VUSE/VDEFs of GCC. Thanks for the comment! I am not aware of anything along these lines, although it would be quite helpful. The pass spends a significant amount of time running the aliasing-analysis queries. -Hal > > I was trying to find a similar representation in LLVM: isn't there already &...

...__ASSEMBLY__ +/* + * Create VMI_CALL_FuncName definitions for assembly code using + * equates; the C enumerations can not be used without propagating + * them in some fashion, and rather the obfuscate asm-offsets.c, it + * seems reasonable to confine this here. + */ +.equ VMI_CALL_CUR, 0; +#define VDEF(call) \ + .equ VMI_CALL_/**/call, VMI_CALL_CUR; \ + .equ VMI_CALL_CUR, VMI_CALL_CUR+1; +VMI_CALLS +#undef VDEF +#endif /* __ASSEMBLY__ */ + +#define IRET vmi_raw_call(VMI_CALL_IRET, iret) +#define CLI vmi_raw_call(VMI_CALL_DisableInterrupts, cli) +#define STI vmi_raw_call(VMI_CALL_EnableInter...

...__ASSEMBLY__ +/* + * Create VMI_CALL_FuncName definitions for assembly code using + * equates; the C enumerations can not be used without propagating + * them in some fashion, and rather the obfuscate asm-offsets.c, it + * seems reasonable to confine this here. + */ +.equ VMI_CALL_CUR, 0; +#define VDEF(call) \ + .equ VMI_CALL_/**/call, VMI_CALL_CUR; \ + .equ VMI_CALL_CUR, VMI_CALL_CUR+1; +VMI_CALLS +#undef VDEF +#endif /* __ASSEMBLY__ */ + +#define IRET vmi_raw_call(VMI_CALL_IRET, iret) +#define CLI vmi_raw_call(VMI_CALL_DisableInterrupts, cli) +#define STI vmi_raw_call(VMI_CALL_EnableInter...

...roc_vmi_info_open(struct inode *inode, struct file *file) +{ + return single_open(file, proc_vmi_info_show, NULL); +} + +static struct file_operations proc_vmi_info_operations = { + .open = proc_vmi_info_open, + .read = seq_read, + .llseek = seq_lseek, + .release = single_release, +}; + +#define VDEF(call) #call , +static char *vmi_call_name[] = { + VMI_CALLS +}; +#undef VDEF + +static void print_annotation(struct seq_file *m, struct vmi_annotation *a) +{ + seq_printf(m, "%s %p %d %p %d %d\n", + vmi_call_name[a->vmi_call], a->nativeEIP, a->native_size, + a->tran...

...roc_vmi_info_open(struct inode *inode, struct file *file) +{ + return single_open(file, proc_vmi_info_show, NULL); +} + +static struct file_operations proc_vmi_info_operations = { + .open = proc_vmi_info_open, + .read = seq_read, + .llseek = seq_lseek, + .release = single_release, +}; + +#define VDEF(call) #call , +static char *vmi_call_name[] = { + VMI_CALLS +}; +#undef VDEF + +static void print_annotation(struct seq_file *m, struct vmi_annotation *a) +{ + seq_printf(m, "%s %p %d %p %d %d\n", + vmi_call_name[a->vmi_call], a->nativeEIP, a->native_size, + a->tran...

...g Since my "error" doesn't look like noise ( is strongly autocorrelated) did I make any mistakes? Thank you for reading down to this line... I hope you have suggestions! Thanks Andrea ########################### Here's a sample of data: > data[1:10,] time force vdef hdef 1 0.0000 0.000 0.000 0.000 2 0.0025 -0.007 -0.229 0.000 3 0.0050 -0.166 -1.829 0.453 4 0.0075 -0.544 -7.086 2.038 5 0.0100 -0.957 -13.714 3.849 6 0.0125 -1.304 -19.886 5.660 7 0.0150 -1.550 -25.143 7.245 8 0.0175 -1.719 -29.714 8.377 9 0.0200 -1.838 -33.372 9.510 10 0...

...etails. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + * + * Send feedback to zach@vmware.com + * + */ + +#include <vmiCalls.h> + +#define VDEF(name) \ + . = __VMI_NEXT; \ + __VMI_NEXT = . + 32; \ + *(.text.VMI_##name); + +#define MACH_TEXT \ +. = ALIGN(4096); \ +__VMI_START = .; \ +__VMI_NEXT = .; \ +__VMI_END = . + 16384; \ +VMI_CALLS \ +. = __VMI_END; \ +. = ALIGN(4096); Index: linux-2.6.16-rc3/include/asm-i386/mach-default/mach-v...

...etails. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + * + * Send feedback to zach@vmware.com + * + */ + +#include <vmiCalls.h> + +#define VDEF(name) \ + . = __VMI_NEXT; \ + __VMI_NEXT = . + 32; \ + *(.text.VMI_##name); + +#define MACH_TEXT \ +. = ALIGN(4096); \ +__VMI_START = .; \ +__VMI_NEXT = .; \ +__VMI_END = . + 16384; \ +VMI_CALLS \ +. = __VMI_END; \ +. = ALIGN(4096); Index: linux-2.6.16-rc3/include/asm-i386/mach-default/mach-v...

...x of 32-bit float (128 bits total) <4 x c64> - Vector of four complex of 64-bit float (512 bits total) ... Such vectors may be scalable: <vscale x 8 x c16> <vscale x 4 x c32> <vscale x 1 x c64> <vscale x 2 x c64> ... Analogous ValueTypes will be used by intrinsics. vdef c16 : ValueType<32, uuu> def c32 : ValueType<64, vvv> def c64 : ValueType<128, www> def x86c80 : ValueType<160, xxx> def c128 : ValueType<256, yyy> def ppcc128 : ValueType<256, zzz> def v8c16 : ValueType<128, aaa> def v4c3...

...omplex of 64-bit float (512 bits total) > ... > > Such vectors may be scalable: > > <vscale x 8 x c16> > <vscale x 4 x c32> > <vscale x 1 x c64> > <vscale x 2 x c64> > ... > > Analogous ValueTypes will be used by intrinsics. > > vdef c16 : ValueType<32, uuu> > def c32 : ValueType<64, vvv> > def c64 : ValueType<128, www> > def x86c80 : ValueType<160, xxx> > def c128 : ValueType<256, yyy> > def ppcc128 : ValueType<256, zzz> > > def v8c16...

Tobias, I've attached an updated copy of the patch. I believe that I accounted for all of your suggestions except for: 1. You said that I could make AA a member of the class and initialize it for each basic block. I suppose that I'd need to make it a pointer, but more generally, what is the thread-safely model that I should have in mind for the analysis passes (will multiple threads

On 11/23/2011 05:52 PM, Hal Finkel wrote: > On Mon, 2011-11-21 at 21:22 -0600, Hal Finkel wrote: >> > On Mon, 2011-11-21 at 11:55 -0600, Hal Finkel wrote: >>> > > Tobias, >>> > > >>> > > I've attached an updated patch. It contains a few bug fixes and many >>> > > (refactoring and coding-convention) changes inspired