search for: bndmov

...cation allows the metadata to be stored either in look-aside tables or explicitly managed. > > Is it? Which specification are you referring to? > http://download-software.intel.com/sites/default/files/319433-015.pdf (chapter 9) doesn't say anything like this. (Or does it?) See the BNDMOV instruction, which allows the bounds to be explicitly loaded and stored to bounds registers. Contrast with BNDLDX / BNDSTX, where the location is implicit. The BNDMOV instruction is also used for stack spills of the bounds registers. This allows MPX to be used for range checking in a similar way...

...ta > to be stored either in look-aside tables or explicitly managed. > > > > Is it? Which specification are you referring to? > > http://download-software.intel.com/sites/default/files/319433-015.pdf(chapter 9) doesn't say anything like this. (Or does it?) > > See the BNDMOV instruction, which allows the bounds to be explicitly > loaded and stored to bounds registers. Contrast with BNDLDX / BNDSTX, > where the location is implicit. The BNDMOV instruction is also used for > stack spills of the bounds registers. This allows MPX to be used for range > check...

On Tue, Sep 10, 2013 at 1:19 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk > wrote: > On 10 Sep 2013, at 10:13, Kostya Serebryany <kcc at google.com> wrote: > > > How did you come with 320 bits? > > 320=64*4+64, which is the size of the metadata table entry plus pointer > size, > > > Sorry, that should have been 192. The specification allows the

On 10 Sep 2013, at 12:13, Kostya Serebryany <kcc at google.com> wrote: > Well, ok, you can treat this as a 192-bit fat pointer, but AFAICT this is not the real intention of the MPX developers > since a fat pointer will break all ABIs, and MPX tries to preserve them. MPX is an implementation of the HardBound concept from UPenn, where this was a design goal (see also their 'low-fat

....cfi_offset %rbp, -16 movq %rsp, %rbp .cfi_def_cfa_register %rbp xorl %eax, %eax leaq -4(%rbp), %poi0 leaq -32(%rbp), %rcx movq %rcx, %poi1 leaq -4(%rbp), %rcx movq %rcx, %poi2 movaps %poi2, (%poi1) bndmov %poi0, -48(%rbp) # 16-byte Folded Spill popq %rbp retq The instructions in red should not be there, otherwise, everything is fine. Does anyone know what could be causing this? Thanks, Barbora -- ---------------- Barbora Murinová The University of Edinburgh SK: +421905...