Displaying 3 results from an estimated 3 matches for "intel_iapx_432".
2008 Apr 16
1
[LLVMdev] Being able to know the jitted code-size before emitting
Am Mittwoch, den 16.04.2008, 00:05 -0700 schrieb Evan Cheng:
> Hrm. Are there machines where
> instructions may not be byte sized?
The iAPX 432 had a bitstream format.
See http://en.wikipedia.org/wiki/Intel_iAPX_432 .
In a nutshell: the processor was a failure due to many reasons, the
bitstream format among them though not particularly prominent.
> > +static unsigned sizeGlobalAddress(bool dword) {
> > + if (dword)
> > + return 8;
> > + else
> > + return 4;
> > +}
&...
2008 Apr 16
0
[LLVMdev] Being able to know the jitted code-size before emitting
Comments below.
On Apr 15, 2008, at 4:24 AM, Nicolas Geoffray wrote:
> OK, here's a new patch that adds the infrastructure and the
> implementation for X86, ARM and PPC of GetInstSize and
> GetFunctionSize. Both functions are virtual functions defined in
> TargetInstrInfo.h.
>
> For X86, I moved some commodity functions from X86CodeEmitter to
> X86InstrInfo.
>
2008 Apr 15
4
[LLVMdev] Being able to know the jitted code-size before emitting
OK, here's a new patch that adds the infrastructure and the
implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize.
Both functions are virtual functions defined in TargetInstrInfo.h.
For X86, I moved some commodity functions from X86CodeEmitter to
X86InstrInfo.
What do you think?
Nicolas
Evan Cheng wrote:
>
> I think both of these belong to TargetInstrInfo. And