Aquileo | Recent changes to feature-requests

Aquileo | New(?) opcodes

2018-07-07T08:56:00.307000Z

Please add opcodes for endbr32/endbr64 (see https://software.intel.com/sites/default/files/managed/4d/2a/control-flow-enforcement-technology-preview.pdf).

Aquileo | Ability to enable deprecated/experimental features via command line flags

2016-06-28T15:18:23.678000Z

For the sake of backward compatibility, it seems reasonable to hide the deprecated functionality behind the cmd flag instead of completely removing it.
The same may be applied to experimental features in order to beta-test them, for instance.

The reason I raise it -- is the removal of the context-through lookup (http://www.nasm.us/doc/nasmdoc4.html#section-4.7.4).
I agree that this feature is dangerous and can lead to quite tricky problems, but when the programmer uses it consciously, it may appear very useful or even irreplaceable.
I would take an older version, but that means I shall get no further fixes, and features.

Thank you.

Aquileo | #196 Support self-relative addresses to data

2013-07-27T07:48:37.389000Z

Sorry. I have moved it to
http://bugzilla.nasm.us/show_bug.cgi?id=3392263

Aquileo | #176 Negative relocations (bin)

2013-07-26T20:08:43.523000Z

Negative relocations are not possible in any of the object file format I have seen.

Yes. And?

Besides, as you likely know, the bin output format of NASM isn't exactly an object format. It is more akin to a linker's output format.

You probably need a self-relative relocation. See feature request 196

I do not. I now and then find cases where relocations with multipliers other than one would be useful, even beyond what can be covered by the specific case of self-relativ relocations.

Aquileo | #196 Support self-relative addresses to data

2013-07-26T11:37:40.518000Z

Could you please use bugzilla.nasm.us for future requests, we're trying to minimize use of SF buckracking.

Aquileo | #176 Negative relocations (bin)

2013-07-26T11:35:08.856000Z

Negative relocations are not possible in any of the object file format I have seen.
You probably need a self-relative relocation. See feature request 196

https://sourceforge.net/p/nasm/feature-requests/196/

Aquileo | #176 Negative relocations (bin)

2013-07-26T11:33:19.966000Z

Negative relocations are not supported in any of the object file formats I have seen. You probably need a self-relative relocation.
See feature request # 196

https://sourceforge.net/p/nasm/feature-requests/196/

Aquileo | Support self-relative addresses to data

2013-07-26T11:31:03.135000Z

NASM does not support self-relative addresses from code to data, but YASM does. As YASM is no longer maintained, I have to port my code to NASM. Therefore this request.

I am making self-relative code in 32 bit mode without a GOT in this way:

.data
mydata dd 0

.code
call get_esp_into_ecx
ecx_points_here:
mov eax,[ecx + (mydata - ecx_points_here]  ; read mydata
ret

get_esp_into_ecx:
mov ecx,[esp]         ; this function reads its own return address
ret

This is the same method that is used for making position-independent code in a Unix shared object, except I want to get rid of the slow GOT lookup.

As I said, this works in YASM, while NASM says error: beroset-p-637-invalid effective address
What is needed is a self-relative address, similar to the rip-relative address in 64-bit mode.

Aquileo | Support for MASM and TASM ptr directive

2012-04-23T10:10:14Z

I suggest that NASM should have an additional feature to support the 'ptr' directive making previous TASM and MASM users adapt the NASM syntax easily with less difficulty.

Aquileo | add support for VMFUNC instruction

2011-12-21T06:43:14Z

It's documented in version 041 of the Intel manuals, in the section about VMX.

VMFUNC = 0Fh,01h,D4h

EAX is implied as its operand