Lines Matching defs:read
113 read/write and entirely avoid this uglyness. */
295 /* The register buffers. A read-only register cache can hold the
296 full [0 .. NUM_REGS + NUM_PSEUDO_REGS) while a read/write
300 /* Is this a read-only cache? A read-only cache is used for saving
302 call or just before forcing a function return). A read-only
371 /* The DST should be `read-only', if it wasn't then the save would
405 /* The dst had better not be read-only. If it is, the `restore'
428 /* Don't even think about fetching a register from a read-only
628 read/written fall inside of an invalid register. [The main reason
635 Prior to the recent fixes to check for partial updates, both read
652 /* See if we are trying to read bytes from out-of-date registers. If so,
669 /* The range the user wants to read doesn't overlap with regnum. */
681 the entire register read/write flow of control. Must
1059 /* Perform a partial register transfer using a read, modify, write
1070 regcache_read_ftype *read, regcache_write_ftype *write)
1084 gdb_assert (read != NULL);
1085 read (regcache, regnum, reg);