types.hh (5251:8de83cada19d) | types.hh (5668:5b5a9f4203d1) |
---|---|
1/* 2 * Copyright (c) 2007 The Hewlett-Packard Development Company 3 * All rights reserved. 4 * 5 * Redistribution and use of this software in source and binary forms, 6 * with or without modification, are permitted provided that the 7 * following conditions are met: 8 * --- 232 unchanged lines hidden (view full) --- 241 typedef uint64_t FloatRegBits; 242 typedef union 243 { 244 IntReg intReg; 245 FloatReg fpReg; 246 MiscReg ctrlReg; 247 } AnyReg; 248 | 1/* 2 * Copyright (c) 2007 The Hewlett-Packard Development Company 3 * All rights reserved. 4 * 5 * Redistribution and use of this software in source and binary forms, 6 * with or without modification, are permitted provided that the 7 * following conditions are met: 8 * --- 232 unchanged lines hidden (view full) --- 241 typedef uint64_t FloatRegBits; 242 typedef union 243 { 244 IntReg intReg; 245 FloatReg fpReg; 246 MiscReg ctrlReg; 247 } AnyReg; 248 |
249 //XXX This is very hypothetical. X87 instructions would need to 250 //change their "context" constantly. It's also not clear how 251 //this would be handled as far as out of order execution. 252 //Maybe x87 instructions are in order? 253 enum RegContextParam 254 { 255 CONTEXT_X87_TOP 256 }; 257 258 typedef int RegContextVal; 259 | |
260 typedef uint16_t RegIndex; 261 262 struct CoreSpecific { 263 int core_type; 264 }; 265}; 266 267#endif // __ARCH_X86_TYPES_HH__ | 249 typedef uint16_t RegIndex; 250 251 struct CoreSpecific { 252 int core_type; 253 }; 254}; 255 256#endif // __ARCH_X86_TYPES_HH__ |