Recent Posts

Pages: 1 ... 8 9 [10]
91
Programming with NASM / Re: blsi
« Last post by debs3759 on September 22, 2023, 10:54:00 PM »
Hi,

I see BLSI listed in the following document:
https://redirect.cs.umbc.edu/~chang/cs313.s13/nasmdoc/nasmdoc.pdf

However, when I try to compile an asm file with blsi op, I get the following:
blsi.asm:15: error: parser: instruction expected

The line:
    blsi rax, rbx

Am I missing something or nasm doesn't support this instruction?

Thanks

It's listed as a future opcode, so isn't supported yet. I don't know which processor family supports (or will support) it, so you may need to wait a while for someone to add the BM11 and BM12 instruction sets.
92
Programming with NASM / blsi
« Last post by suncowiam on September 22, 2023, 09:52:01 PM »
Hi,

I see BLSI listed in the following document:
https://redirect.cs.umbc.edu/~chang/cs313.s13/nasmdoc/nasmdoc.pdf

However, when I try to compile an asm file with blsi op, I get the following:
blsi.asm:15: error: parser: instruction expected

The line:
    blsi rax, rbx

Am I missing something or nasm doesn't support this instruction?

Thanks
93
NASMX / Re: Announcing NASM-X v1.4
« Last post by Frank Kotler on August 15, 2023, 08:53:09 AM »
Unlikely to work on another cpu. Nothing to lose but your time trying.

Best,
Frank

94
NASMX / Re: Announcing NASM-X v1.4
« Last post by ben321 on August 15, 2023, 07:50:00 AM »
Interesting project, is it possible to use macros with NASM to write assembly code for any architecture? For example, in SNES assembly, there's not the 8 main registers found in an Intel chip. There's only 3 main registers, and they are called A, X, and Y. Is it possible to "teach" NASM, using macros to recognize other registers for other system architectures? Or are its hardcoded Intel register names the only register names that can be used in NASM? How extensible is NASM in terms of using macros to define assembly code for other architectures?
95
Other Discussion / Re: ELF files are confusing.
« Last post by Frank Kotler on August 14, 2023, 01:04:52 PM »
Okay, I'm confused on general principles. :)

Are you straightened out, Ben?

Frank

 
96
Other Discussion / Re: ELF files are confusing.
« Last post by fredericopissarra on August 14, 2023, 12:13:01 PM »
Yeah, I am probably confused. Should have stopped after "I don't know'"

Best,
Frank
Frank, I was talking about the "program headers" in the original post.

[]s
Fred
97
Other Discussion / Re: ELF files are confusing.
« Last post by Frank Kotler on August 13, 2023, 07:58:55 PM »
Thank you!

Frank

98
Other Discussion / Re: ELF files are confusing.
« Last post by vitsoft on August 13, 2023, 07:15:32 PM »
While ELF Sections are used by the linker, ELF Program Segments are used by the (dynamic) loader at the Linux program execution.
Section header tells where is the section's contents located in the file. This is used mostly at link-time.

Program segments instruct the loader at load-time about virtual address where should each segment be memory-mapped at, and what privileges should it be assigned (read,write,execute). See also ELF specification.

If you want to inspect ELF files in Windows, install Linux emulator WSL and use
readelf -aW ElfFile
99
Other Discussion / Re: ELF files are confusing.
« Last post by Frank Kotler on August 12, 2023, 04:01:43 AM »
Yeah, I am probably confused. Should have stopped after "I don't know'"

Best,
Frank

100
Other Discussion / Re: ELF files are confusing.
« Last post by fredericopissarra on August 11, 2023, 11:55:00 AM »
Aren't you confusing with "Program Header Table"?

In general, ELF is simplier then PE (and PE+).
Pages: 1 ... 8 9 [10]