I am not 100% sure, but I think those definitions are given in the softmmu_header.h file.
This file will be included several times in the exec-all.h (see line 272 and following) and softmmu_exec.h with different defines for DATA_SIZE (for b,w,l,q) and MEMSUFFIX (for _kernel, _user etc.). Inside the softmmu_header.h they use some spooky macro magic to glue all those things together to define all possible flavors for the ld/st functions. This is where the magic takes place: "static inline RES_TYPE glue(glue(ld, USUFFIX), MEMSUFFIX)(target_ulong ptr)" So from my point of view this should also be defined if the CONFIG_USER_ONLY is not defined. Hope this will help you. Regards, Stefan Edit: FW for the mailing list. 2012/2/8 Teng-Feng Yang <[email protected]> > Hi > > Recently I find a bug related to these memory access functions (*ldub_code > *, *ldub_kernel*, and *ldub_user*) in my own project. > When I try to find the definitions of these functions, I only find > possible matches in *qemu/cpu-all.h *when *CONFIG_USER_ONLY* is set. > It seems that these functions will call *ldub_p* eventually; however, I > can't find the definitions when *CONFIG_USER_ONLY* is not set (DEFAULT). > > Any help would be grateful! > > Thanks > > Dennis > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
