issue_owner_repo
listlengths 2
2
| issue_body
stringlengths 0
261k
⌀ | issue_title
stringlengths 1
925
| issue_comments_url
stringlengths 56
81
| issue_comments_count
int64 0
2.5k
| issue_created_at
stringlengths 20
20
| issue_updated_at
stringlengths 20
20
| issue_html_url
stringlengths 37
62
| issue_github_id
int64 387k
2.46B
| issue_number
int64 1
127k
|
|---|---|---|---|---|---|---|---|---|---|
[
"yasm",
"yasm"
] |
I'm using macOS 10.15 and Xcode 11.2.1 and building ffmpeg on macOS and then link it to my project targeting macOS 10.12. When linking the linker gives such warnings:
```
ld: warning: building for macOS, but linking in object file (/Users/preston/Telegram/Libraries/macos/ffmpeg/libswscale/libswscale.a(input.o)) built for free standing
```
For all object files that were built using YASM.
For C and C++ sources additional compiler options are passed to Apple Clang: "-mmacosx-version-min=10.12" and this removes such problems for object files built from C / C++ sources. I guess it puts something like this in the object file:
```
Load command 1
cmd LC_VERSION_MIN_MACOSX
cmdsize 16
version 10.12
sdk 10.15
```
and this information is read by the linker and it doesn't complain.
Is it possible to add a flag to pass on macOS to YASM so that it will write such section as well? Those warnings are noisy and it seems they can't be disabled.
Other compilers (Crystal, Go, D) have (or had) this problem as well, see: https://github.com/golang/go/issues/33214#issuecomment-541353859
|
Allow including target system information in objects on macOS.
|
https://api.github.com/repos/yasm/yasm/issues/141/comments
| 8 |
2019-11-29T10:41:26Z
|
2023-04-12T11:01:26Z
|
https://github.com/yasm/yasm/issues/141
| 530,276,869 | 141 |
[
"yasm",
"yasm"
] |
wget https://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz
--2019-11-28 21:00:34-- https://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz
ERROR: cannot verify www.tortall.net's certificate, issued by ‘CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US’:
Unable to locally verify the issuer's authority.
To connect to www.tortall.net insecurely, use `--no-check-certificate'.
|
Yasm download. CERT Expired.
|
https://api.github.com/repos/yasm/yasm/issues/140/comments
| 1 |
2019-11-28T15:33:10Z
|
2023-12-12T18:26:30Z
|
https://github.com/yasm/yasm/issues/140
| 529,976,743 | 140 |
[
"yasm",
"yasm"
] |
I'm tried compile this code:
```
bits 32
push ebx
push dword ebx
push strict dword ebx
```
but llvm-objdump shows that assembler emit pushw instruction.
If I run compiler on x86 host, it works correctly.
|
Yasm does not affect "dword" and "strict" keywords in push command on arm host
|
https://api.github.com/repos/yasm/yasm/issues/139/comments
| 2 |
2019-11-05T07:54:16Z
|
2019-11-05T09:37:11Z
|
https://github.com/yasm/yasm/issues/139
| 517,603,871 | 139 |
[
"yasm",
"yasm"
] |
```
section data1 data
use32
db 'short',0
section data2 bss
use32
resb 100
```
```
yasm -fwin32 test2.s
objdump -x test2.obj
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00000000 00000000 00000000 00000000 2**4
ALLOC, LOAD, READONLY, CODE
1 data1 00000006 00000000 00000000 0000008c 2**2
CONTENTS, ALLOC, LOAD, DATA
2 data2 00000006 00000000 00000000 00000000 2**2
ALLOC
```
data2 size should be 100 not 6. nasm gets this right
```
nasm -fwin32 test2.s
objdump -x test2.obj
Sections:
Idx Name Size VMA LMA File off Algn
0 data1 00000006 00000000 00000000 00000064 2**2
CONTENTS, ALLOC, LOAD, DATA
1 data2 00000064 00000000 00000000 00000000 2**2
ALLOC
|
Named bss section size incorrect on win32 target
|
https://api.github.com/repos/yasm/yasm/issues/137/comments
| 1 |
2019-10-04T18:46:18Z
|
2019-10-04T19:26:55Z
|
https://github.com/yasm/yasm/issues/137
| 502,788,599 | 137 |
[
"yasm",
"yasm"
] |
I know this is an issue with RHEL, but I don't know where to start by contacting them about it. Maybe someone over here knows what's up?
|
Missing on centos 8
|
https://api.github.com/repos/yasm/yasm/issues/136/comments
| 2 |
2019-09-25T13:46:37Z
|
2019-10-03T16:34:49Z
|
https://github.com/yasm/yasm/issues/136
| 498,298,364 | 136 |
[
"yasm",
"yasm"
] |
My builds are failing due to:
`curl -I https://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz`
`curl: (7) Failed to connect to www.tortall.net port 443: Connection refused`
|
https://www.tortall.net/ is down
|
https://api.github.com/repos/yasm/yasm/issues/135/comments
| 6 |
2019-07-23T18:16:13Z
|
2021-08-11T13:50:14Z
|
https://github.com/yasm/yasm/issues/135
| 471,849,316 | 135 |
[
"yasm",
"yasm"
] |
<details>
```console
+ /usr/bin/make -O -j48 V=1 VERBOSE=1 check
/usr/bin/make check-recursive
Making check in po
make[2]: Nothing to be done for 'check'.
Making check in .
/usr/bin/make test_hd bitvect_test floatnum_test leb128_test splitpath_test combpath_test uncstring_test
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o test_hd.o test_hd.c
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
libyasm/tests/splitpath_test.c: In function 'main':
libyasm/tests/splitpath_test.c:147:21: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
147 | sprintf(failed, "%s ** F: %s\n", failed, failmsg);
| ^~~~~~ ~~~~~~
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o libyasm/tests/splitpath_test.o libyasm/tests/splitpath_test.c
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
libyasm/tests/uncstring_test.c: In function 'main':
libyasm/tests/uncstring_test.c:147:21: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
147 | sprintf(failed, "%s ** F: %s\n", failed, failmsg);
| ^~~~~~ ~~~~~~
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o libyasm/tests/uncstring_test.o libyasm/tests/uncstring_test.c
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o libyasm/tests/combpath_test.o libyasm/tests/combpath_test.c
libyasm/tests/combpath_test.c: In function 'main':
libyasm/tests/combpath_test.c:132:21: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
132 | sprintf(failed, "%s ** F: %s\n", failed, failmsg);
| ^~~~~~ ~~~~~~
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
libyasm/tests/bitvect_test.c: In function 'runtest_':
libyasm/tests/bitvect_test.c:158:17: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
158 | sprintf(failed, "%s ** F: %s failed!\n", failed, testname);
| ^~~~~~ ~~~~~~
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o libyasm/tests/bitvect_test.o libyasm/tests/bitvect_test.c
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
libyasm/tests/floatnum_test.c: In function 'runtest_':
libyasm/tests/floatnum_test.c:426:17: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
426 | sprintf(failed, "%s ** F: %s failed: %s!\n", failed, testname,
| ^~~~~~ ~~~~~~
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o libyasm/tests/floatnum_test.o libyasm/tests/floatnum_test.c
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
libyasm/tests/leb128_test.c: In function 'main':
libyasm/tests/leb128_test.c:182:21: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
182 | sprintf(failed, "%s ** F: %s\n", failed, failmsg);
| ^~~~~~ ~~~~~~
libyasm/tests/leb128_test.c:189:21: warning: passing argument 1 to restrict-qualified parameter aliases with argument 3 [-Wrestrict]
189 | sprintf(failed, "%s ** F: %s\n", failed, failmsg);
| ^~~~~~ ~~~~~~
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -DHAVE_CONFIG_H -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -c -o libyasm/tests/leb128_test.o libyasm/tests/leb128_test.c
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o test_hd test_hd.o
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o splitpath_test libyasm/tests/splitpath_test.o libyasm.a
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o uncstring_test libyasm/tests/uncstring_test.o libyasm.a
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o bitvect_test libyasm/tests/bitvect_test.o libyasm.a
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o combpath_test libyasm/tests/combpath_test.o libyasm.a
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o leb128_test libyasm/tests/leb128_test.o libyasm.a
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto -fuse-linker-plugin -o floatnum_test libyasm/tests/floatnum_test.o libyasm.a
make[3]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
/usr/bin/make check-TESTS
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: bitvect_test
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: combpath_test
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: leb128_test
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: splitpath_test
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: floatnum_test
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: uncstring_test
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/parsers/nasm/tests/worphan/nasm_worphan_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/parsers/tasm/tests/exe/tasm_exe_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/dbgfmts/dwarf2/tests/gen64/dwarf2_gen64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/preprocs/raw/tests/rawpp_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/dbgfmts/dwarf2/tests/passwin64/dwarf2_passwin64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/dbgfmts/stabs/tests/stabs_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/macho/tests/gas32/gas_macho32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/win64/tests/gas/win64_gas_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/dbgfmts/dwarf2/tests/pass32/dwarf2_pass32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/preprocs/tasm/tests/tasmpp_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/elf/tests/gas32/elf_gas32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/macho/tests/gas64/gas_macho64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/macho/tests/nasm64/macho64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/win32/tests/gas/win32_gas_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/arch/lc3b/tests/lc3b_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
FAIL: modules/objfmts/elf/tests/gas64/elf_gas64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/elf/tests/gasx32/elf_gasx32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/dbgfmts/dwarf2/tests/pass64/dwarf2_pass64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/elf/tests/x32/elf_x32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/macho/tests/nasm32/macho32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/win32/tests/win32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/coff/tests/coff_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/rdf/tests/rdf_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/preprocs/nasm/tests/nasmpp_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/arch/x86/tests/gas32/x86_gas32_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/xdf/tests/xdf_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/bin/tests/bin_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/parsers/gas/tests/bin/gas_bin_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/win64/tests/win64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/arch/x86/tests/gas64/x86_gas64_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/parsers/tasm/tests/tasm_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/bin/tests/multisect/bin_multi_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/parsers/gas/tests/gas_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/parsers/nasm/tests/nasm_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/objfmts/elf/tests/elf_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: libyasm/tests/libyasm_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
PASS: modules/arch/x86/tests/x86_test.sh
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
make[4]: *** [Makefile:3252: test-suite.log] Error 1
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/yasm-1.3.0'
==================================
yasm 1.3.0: ./test-suite.log
==================================
# TOTAL: 44
# PASS: 42
# SKIP: 0
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh
=======================================================
```
</details>
|
1.3.0: test suite fails
|
https://api.github.com/repos/yasm/yasm/issues/134/comments
| 6 |
2019-07-04T20:38:18Z
|
2024-03-21T21:19:32Z
|
https://github.com/yasm/yasm/issues/134
| 464,389,718 | 134 |
[
"yasm",
"yasm"
] |
It is almost 5 years since last yasm release.
I think that it would be good to push current set of committed changes and release new code base :)
|
Any plans to make new release?
|
https://api.github.com/repos/yasm/yasm/issues/133/comments
| 2 |
2019-07-04T20:27:23Z
|
2023-12-12T18:27:04Z
|
https://github.com/yasm/yasm/issues/133
| 464,387,605 | 133 |
[
"yasm",
"yasm"
] |
```
root@evandro-pc:~# apt-get install yasm
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package yasm
root@evandro-pc:~# apt-get install nasm
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package nasm
```
|
How to install it on Ubuntu 16.04?
|
https://api.github.com/repos/yasm/yasm/issues/131/comments
| 2 |
2019-03-28T16:30:05Z
|
2020-08-26T17:33:14Z
|
https://github.com/yasm/yasm/issues/131
| 426,591,499 | 131 |
[
"yasm",
"yasm"
] |
The powershell code to download files such as the yasm executable doesn't work when executed from behind a corporate firewall. To make the script work I changed the powershell command to use wget instead, which has provision for corporate firewalls via the HTTP_PROXY environment variable. I found I had to use CNTLM as well which is also common in corporate environments. So I think install_script needs to take these things into account.
I am *not* proposing that the script be changed to use wget. I just used that because I don't know powershell.
|
install_script.bat does not work behind a corporate firewall
|
https://api.github.com/repos/yasm/yasm/issues/130/comments
| 0 |
2019-02-13T08:32:19Z
|
2019-02-13T08:32:19Z
|
https://github.com/yasm/yasm/issues/130
| 409,684,072 | 130 |
[
"yasm",
"yasm"
] |
Please consider adding a digital signature to the yasm executable that is available on the web site. Without a digital signature yasm is blocked by CarbonBlack (aka bit9). This sort of blocking is common in corporate environments and prevents yasm being used there.
|
yasm.exe is not signed, so it gets blocked by CarbonBlack (aka bit9)
|
https://api.github.com/repos/yasm/yasm/issues/129/comments
| 0 |
2019-02-13T08:28:08Z
|
2019-02-13T08:28:08Z
|
https://github.com/yasm/yasm/issues/129
| 409,682,546 | 129 |
[
"yasm",
"yasm"
] |
The last release is from 2014, while not too much development happened, it still contains multiple fixes.
Please consider pushing a new git tag, thanks
|
please tag a new release
|
https://api.github.com/repos/yasm/yasm/issues/128/comments
| 0 |
2019-02-12T01:30:27Z
|
2019-02-12T01:30:27Z
|
https://github.com/yasm/yasm/issues/128
| 409,068,676 | 128 |
[
"yasm",
"yasm"
] |
I used VS2017, built from the latest source, and the release sizes were 60% larger than the ones pre-built on the original 1.3.0 release. Looking at the commits, it doesn't look like 300+K of code changes were made and doesn't look like the released .exe versions are compressed with upx or mpress.
I need the updated versions to fix problems with vsyasm not allowing Win32 parameter (case sensitivity issue). Is this safe or is something fishy going on?
?
|
Why are windows .exe 60% larger when I build vs release build?
|
https://api.github.com/repos/yasm/yasm/issues/127/comments
| 2 |
2018-11-29T19:21:22Z
|
2018-11-29T21:34:19Z
|
https://github.com/yasm/yasm/issues/127
| 385,887,779 | 127 |
[
"yasm",
"yasm"
] |
`echo "cHVzaM4kLSQmJC0kJi0kLTA=" | base64 -d | tee test.asm && ./yasm test.asm`
```
==1322==ERROR: AddressSanitizer: heap-use-after-free on address 0x606000000bd0 at pc 0x00000062744b bp 0x7ffe72c32aa0 sp 0x7ffe72c32a98
READ of size 4 at 0x606000000bd0 thread T0
#0 0x62744a in expr_traverse_nodes_post /root/yasm/libyasm/expr.c:1226:20
#1 0x62b53c in yasm_expr_destroy /root/yasm/libyasm/expr.c:1159:5
#2 0x62b53c in expr_delete_term /root/yasm/libyasm/expr.c:1138
#3 0x62b53c in expr_simplify_identity /root/yasm/libyasm/expr.c:582
#4 0x622658 in expr_level_op /root/yasm/libyasm/expr.c:701:17
#5 0x62548e in expr_level_tree /root/yasm/libyasm/expr.c:986:9
#6 0x62863a in yasm_expr__level_tree /root/yasm/libyasm/expr.c:1020:9
#7 0x62863a in yasm_expr_get_intnum /root/yasm/libyasm/expr.c:1375
#8 0x54c66d in recalc_normal_span /root/yasm/libyasm/section.c:1033:15
#9 0x547c61 in yasm_object_optimize /root/yasm/libyasm/section.c:1381:20
#10 0x4f44c8 in do_assemble /root/yasm/frontends/yasm/yasm.c:531:5
#11 0x4f44c8 in main /root/yasm/frontends/yasm/yasm.c:753
#12 0x7fb903ab71c0 in __libc_start_main /build/glibc-itYbWN/glibc-2.26/csu/../csu/libc-start.c:308
#13 0x41ad59 in _start (/root/yasm/yasm+0x41ad59)
0x606000000bd0 is located 16 bytes inside of 56-byte region [0x606000000bc0,0x606000000bf8)
freed by thread T0 here:
#0 0x4c3162 in __interceptor_free /b/swarming/w/ir/kitchen-workdir/src/third_party/llvm/compiler-rt/lib/asan/asan_malloc_linux.cc:124:3
#1 0x627419 in expr_destroy_each /root/yasm/libyasm/expr.c:1151:5
#2 0x627419 in expr_traverse_nodes_post /root/yasm/libyasm/expr.c:1233
#3 0x62b53c in yasm_expr_destroy /root/yasm/libyasm/expr.c:1159:5
#4 0x62b53c in expr_delete_term /root/yasm/libyasm/expr.c:1138
#5 0x62b53c in expr_simplify_identity /root/yasm/libyasm/expr.c:582
#6 0x622658 in expr_level_op /root/yasm/libyasm/expr.c:701:17
#7 0x62548e in expr_level_tree /root/yasm/libyasm/expr.c:986:9
#8 0x62863a in yasm_expr__level_tree /root/yasm/libyasm/expr.c:1020:9
#9 0x62863a in yasm_expr_get_intnum /root/yasm/libyasm/expr.c:1375
#10 0x54c66d in recalc_normal_span /root/yasm/libyasm/section.c:1033:15
#11 0x547c61 in yasm_object_optimize /root/yasm/libyasm/section.c:1381:20
#12 0x4f44c8 in do_assemble /root/yasm/frontends/yasm/yasm.c:531:5
#13 0x4f44c8 in main /root/yasm/frontends/yasm/yasm.c:753
#14 0x7fb903ab71c0 in __libc_start_main /build/glibc-itYbWN/glibc-2.26/csu/../csu/libc-start.c:308
previously allocated by thread T0 here:
#0 0x4c34e3 in malloc /b/swarming/w/ir/kitchen-workdir/src/third_party/llvm/compiler-rt/lib/asan/asan_malloc_linux.cc:146:3
#1 0x558f90 in def_xmalloc /root/yasm/libyasm/xmalloc.c:69:14
#2 0x626da8 in yasm_expr__copy_except /root/yasm/libyasm/expr.c:1112:9
#3 0x626da8 in expr_item_copy /root/yasm/libyasm/expr.c:1086
#4 0x626ac4 in yasm_expr__copy_except /root/yasm/libyasm/expr.c:1120:13
#5 0x54c4b3 in recalc_normal_span /root/yasm/libyasm/section.c:1024:31
#6 0x547c61 in yasm_object_optimize /root/yasm/libyasm/section.c:1381:20
#7 0x4f44c8 in do_assemble /root/yasm/frontends/yasm/yasm.c:531:5
#8 0x4f44c8 in main /root/yasm/frontends/yasm/yasm.c:753
#9 0x7fb903ab71c0 in __libc_start_main /build/glibc-itYbWN/glibc-2.26/csu/../csu/libc-start.c:308
SUMMARY: AddressSanitizer: heap-use-after-free /root/yasm/libyasm/expr.c:1226:20 in expr_traverse_nodes_post
```
|
heap-use-after-free (READ of size 4) in expr_traverse_nodes_post
|
https://api.github.com/repos/yasm/yasm/issues/126/comments
| 0 |
2018-11-12T22:57:29Z
|
2018-11-12T22:57:29Z
|
https://github.com/yasm/yasm/issues/126
| 379,985,797 | 126 |
[
"yasm",
"yasm"
] |
`echo "Y3B1ezMwMDAwMDAwMDAw" | base64 -d | tee test.asm | ./yasm test.asm`
```
==26150==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fff49b911b0 at pc 0x00000044195e bp 0x7fff49b91080 sp 0x7fff49b90808
WRITE of size 21 at 0x7fff49b911b0 thread T0
#0 0x44195d in vsprintf /b/swarming/w/ir/kitchen-workdir/src/third_party/llvm/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:1629:1
#1 0x442f83 in __interceptor_sprintf /b/swarming/w/ir/kitchen-workdir/src/third_party/llvm/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:1672:1
#2 0x55b089 in x86_dir_cpu /root/yasm/modules/arch/x86/x86arch.c:169:17
#3 0x545ca8 in yasm_object_directive /root/yasm/libyasm/section.c:382:5
#4 0x58b188 in nasm_parser_directive /root/yasm/modules/parsers/nasm/nasm-parse.c:1569:10
#5 0x5884dc in parse_line /root/yasm/modules/parsers/nasm/nasm-parse.c:377:17
#6 0x5884dc in nasm_parser_parse /root/yasm/modules/parsers/nasm/nasm-parse.c:231
#7 0x586648 in nasm_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:66:5
#8 0x586648 in nasm_parser_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:83
#9 0x4f446c in do_assemble /root/yasm/frontends/yasm/yasm.c:521:5
#10 0x4f446c in main /root/yasm/frontends/yasm/yasm.c:753
#11 0x7f74827801c0 in __libc_start_main /build/glibc-itYbWN/glibc-2.26/csu/../csu/libc-start.c:308
#12 0x41ad59 in _start (/root/yasm/yasm+0x41ad59)
Address 0x7fff49b911b0 is located in stack of thread T0 at offset 48 in frame
#0 0x55aedf in x86_dir_cpu /root/yasm/modules/arch/x86/x86arch.c:153
This frame has 1 object(s):
[32, 48) 'strcpu' (line 168) <== Memory access at offset 48 overflows this variable
HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow /b/swarming/w/ir/kitchen-workdir/src/third_party/llvm/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:1629:1 in vsprintf
```
|
stack-buffer-overflow (WRITE of size 21) while attempting to assemble crafted code
|
https://api.github.com/repos/yasm/yasm/issues/125/comments
| 0 |
2018-11-12T16:29:27Z
|
2018-11-12T16:29:27Z
|
https://github.com/yasm/yasm/issues/125
| 379,855,247 | 125 |
[
"yasm",
"yasm"
] |
RISC-V is a promising instruction set, from the looks of it. It would be neat to have YASM support RISC-V.
|
Supporting RISC-V
|
https://api.github.com/repos/yasm/yasm/issues/124/comments
| 2 |
2018-11-03T12:54:11Z
|
2019-10-27T01:03:22Z
|
https://github.com/yasm/yasm/issues/124
| 377,052,032 | 124 |
[
"yasm",
"yasm"
] |
How to reproduce:
OS: macOS
Commandline:
git clone https://github.com/yasm/yasm.git yasm
cd yasm
mkdir build && cd build
cmake .. -DCMAKE_BUILD_TYPE=Release -Wno-dev
make
Issue:
It shows compiling errors in nasm-macro.c.
Analysis:
genmacro.c only handles "\n" but not "\r". It reads nasm-std.mac to generate nasm-macro.c, but nasm-std.mac has Windows EOL which is using "\r\n" is line ending. The "\n" is removed by genmacro.c but "\r" is kept and treated as a new line in macOS. Thus it breaks the string in the auto-generated c code.
|
genmacro.c does not handle line ending properly in macOS
|
https://api.github.com/repos/yasm/yasm/issues/122/comments
| 0 |
2018-10-12T20:33:14Z
|
2018-10-12T20:33:14Z
|
https://github.com/yasm/yasm/issues/122
| 369,700,737 | 122 |
[
"yasm",
"yasm"
] |
If the name of the command calling yasm is as (e.g. if someone tried to replace GNU as and so symlinked /usr/bin/yasm to /usr/bin/as), then it would make sense that yasm would automatically run with the parser set to gas.
|
Run with --parser=gas when called as gas
|
https://api.github.com/repos/yasm/yasm/issues/121/comments
| 0 |
2018-10-11T03:50:18Z
|
2018-10-11T03:50:18Z
|
https://github.com/yasm/yasm/issues/121
| 368,941,883 | 121 |
[
"yasm",
"yasm"
] |
--64 is a GNU as flag, so it would make sense that yasm would accept it at least when --parser=gas is used.
|
Support --64 flag when parser=gas
|
https://api.github.com/repos/yasm/yasm/issues/120/comments
| 0 |
2018-10-11T03:48:01Z
|
2018-10-11T03:48:01Z
|
https://github.com/yasm/yasm/issues/120
| 368,941,483 | 120 |
[
"yasm",
"yasm"
] |
how i can install the in my PC please
its say (where the VC++ compiler binaries ) im using VS2017
|
Need help in install
|
https://api.github.com/repos/yasm/yasm/issues/118/comments
| 5 |
2018-09-05T23:21:48Z
|
2018-09-28T14:19:08Z
|
https://github.com/yasm/yasm/issues/118
| 357,438,544 | 118 |
[
"yasm",
"yasm"
] |
Hello!
CMake 2.4 is absolutely ancient, and I'm willing to put in the work to update the current CMakeLists.txt file to a post-3.0 released version. However, rather than do all this work in the event that it gets denied, I figured I would ask first to see if this sort of change would be accepted.
|
Update minimum cmake version
|
https://api.github.com/repos/yasm/yasm/issues/117/comments
| 1 |
2018-09-04T22:12:29Z
|
2022-10-23T20:37:56Z
|
https://github.com/yasm/yasm/issues/117
| 356,994,802 | 117 |
[
"yasm",
"yasm"
] |
I was trying to compile some asm originally written for nasm with yasm, but it fails because yasm doesn't support the `%warning` directive.
So consider this a bug report for that issue, and also a question: "Is there any workaround?" For example, if it was a plain macro I could define it myself (perhaps as a no-op if I couldn't find a way to emulate the warning functionality in yasm.
|
%warning directive not supported
|
https://api.github.com/repos/yasm/yasm/issues/116/comments
| 0 |
2018-09-04T00:51:42Z
|
2018-09-04T00:51:42Z
|
https://github.com/yasm/yasm/issues/116
| 356,619,944 | 116 |
[
"yasm",
"yasm"
] |
Is this a trivial fix? The nasm assembler includes comments in the listing file.
I'm not the only one who could use this, and it would greatly help for educational purposes. I'd also be glad to create a patch, especially if someone could outline the steps required to do this.
https://tortall.lighthouseapp.com/projects/78676/tickets/275-comments-in-listing
|
request: include comments in listing file
|
https://api.github.com/repos/yasm/yasm/issues/115/comments
| 0 |
2018-09-03T21:43:36Z
|
2018-09-04T00:29:24Z
|
https://github.com/yasm/yasm/issues/115
| 356,603,305 | 115 |
[
"yasm",
"yasm"
] |
tools/genmacro/genmacro.c
in line 59: str = malloc(MAXLINE); // memory is allocated
in line 94: return EXIT_FAILURE;// function returned and potential leak of memory pointerd to by 'str'.
|
memory leak
|
https://api.github.com/repos/yasm/yasm/issues/113/comments
| 2 |
2018-08-13T08:38:30Z
|
2018-09-12T07:50:58Z
|
https://github.com/yasm/yasm/issues/113
| 349,936,190 | 113 |
[
"yasm",
"yasm"
] |
The VEX.128 encoding of VPBLENDVB seems to be incorrectly flagged as an AVX2 instruction, attempting to use it in source that contains "cpu noavx2" outputs "warning: 'vpblendvb' is an instruction in CPU" (that's the complete text, seems incomplete) followed by an error because the instruction name is ignored.
|
VPBLENDVB VEX.128 instruction does not require AVX2
|
https://api.github.com/repos/yasm/yasm/issues/111/comments
| 1 |
2018-07-25T08:01:27Z
|
2023-05-15T11:24:57Z
|
https://github.com/yasm/yasm/issues/111
| 344,334,597 | 111 |
[
"yasm",
"yasm"
] |
Hi all,
This is Qihoo360 CodeSafe Team, we found dead code issus in `yasm`, see
https://github.com/yasm/yasm/blob/e256985c4929f4e550d8f70cad5fb936f81b7b06/libyasm/bitvect.c#L300. The `break` statements in `BitVector_Error` seems are all dead code.
|
Dead code issues.
|
https://api.github.com/repos/yasm/yasm/issues/110/comments
| 2 |
2018-07-20T02:50:48Z
|
2018-07-23T02:46:30Z
|
https://github.com/yasm/yasm/issues/110
| 342,954,617 | 110 |
[
"yasm",
"yasm"
] |
`cd ~/ffmpeg_sources && \
wget -O yasm-1.3.0.tar.gz https://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz && \
tar xzvf yasm-1.3.0.tar.gz && \
cd yasm-1.3.0 && \
./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" && \
make && \
make install`
Resolving www.tortall.net (www.tortall.net)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘www.tortall.net’
|
unable to resolve host address ‘www.tortall.net’
|
https://api.github.com/repos/yasm/yasm/issues/109/comments
| 1 |
2018-07-03T13:47:56Z
|
2018-07-03T13:50:51Z
|
https://github.com/yasm/yasm/issues/109
| 337,907,422 | 109 |
[
"yasm",
"yasm"
] |
the certificate for https://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz has expired. Firefox reports:
https://www.tortall.net uses an invalid security certificate. The certificate expired on June 5, 2018, 4:33 AM. The current time is June 5, 2018, 8:10 AM. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
See also: https://github.com/HandBrake/HandBrake/issues/1390
|
certificate for https://www.tortall.net has expired
|
https://api.github.com/repos/yasm/yasm/issues/106/comments
| 6 |
2018-06-05T12:20:20Z
|
2019-07-24T14:06:19Z
|
https://github.com/yasm/yasm/issues/106
| 329,430,698 | 106 |
[
"yasm",
"yasm"
] |
```
$ cat test.asm
dq section.test.vstart * 2
section test
times 128 db 0
$ yasm -f bin -o test.bin test.asm
test.asm:1: error: data expression too complex
```
|
Using special section.?sectname?.* symbols in arithmetic expression yields error: data expression too complex
|
https://api.github.com/repos/yasm/yasm/issues/104/comments
| 0 |
2018-05-07T11:57:56Z
|
2018-05-07T11:58:52Z
|
https://github.com/yasm/yasm/issues/104
| 320,777,056 | 104 |
[
"yasm",
"yasm"
] |
When I try to run yasm in windows 10 ,I get this message.Can anyone help me
|
The code execution cannot proceed because MSVCR100.dll was not found.Reinstalling the program may fix the problem
|
https://api.github.com/repos/yasm/yasm/issues/103/comments
| 1 |
2018-03-08T09:49:00Z
|
2018-03-08T10:02:50Z
|
https://github.com/yasm/yasm/issues/103
| 303,417,528 | 103 |
[
"yasm",
"yasm"
] |
Hi,
On a project, we use Google's libvpx wich is written with Yasm. Everything works fine but for some political reason, one of our first parties require that we use their own assembler (similar to llvm-as I think).
I'm looking for help/advices on how one can port Yasm asm to Gas.
So far, I used Yasm --preproc-only option to get Nasm assembly. I then use intel2gas to do the bulk of the work. I end up with some Gas assembly that makes little to no sens to me with tones of errors that I don't know how to properly fix.
Any advices/help on that matter?
Thanks,
JNQ
|
Yasm to GAS
|
https://api.github.com/repos/yasm/yasm/issues/102/comments
| 0 |
2018-02-09T10:11:29Z
|
2018-02-09T10:11:29Z
|
https://github.com/yasm/yasm/issues/102
| 295,817,960 | 102 |
[
"yasm",
"yasm"
] |
[01org/isa-l_crypto](https://github.com/01org/isa-l_crypto) version 2.20 includes the following configuration snippet:
```
# Check for yasm and yasm features
AC_CHECK_PROG(HAVE_YASM, yasm, yes, no)
if test "$HAVE_YASM" = "no"; then
AC_MSG_RESULT([no yasm])
else
AC_MSG_CHECKING([for modern yasm])
AC_LANG_CONFTEST([AC_LANG_SOURCE([[vmovdqa %xmm0, %xmm1;]])])
if yasm -f elf64 -p gas conftest.c ; then
with_modern_yasm=yes
AC_MSG_RESULT([yes])
AC_MSG_CHECKING([for optional yasm AVX512 support])
AC_LANG_CONFTEST([AC_LANG_SOURCE([[vpshufb %zmm0, %zmm1, %zmm2;]])])
if yasm -f elf64 -p gas conftest.c 2> /dev/null; then
yasm_knows_avx512=yes
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
AC_MSG_CHECKING([for optional yasm SHA-NI support])
AC_LANG_CONFTEST([AC_LANG_SOURCE([[sha256rnds2 %xmm0,%xmm1,%xmm2;]])])
if yasm -f elf64 -p gas conftest.c 2> /dev/null; then
yasm_knows_shani=yes
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
else
AC_MSG_FAILURE([no])
fi
fi
```
As at yasm 1.3.0.36.ge2569, yasm supports neither AVX512 nor SHA-NI, although my interest is just in AVX512 right now.
The output from attempting to compile the AVX512 snippet ``vpshufb %zmm0, %zmm1, %zmm2;`` is
```
avx512.asm:1: error: Unrecognized register name `%zmm0'
avx512.asm:1: error: Unrecognized register name `%zmm1'
```
|
Add support for AVX512.
|
https://api.github.com/repos/yasm/yasm/issues/101/comments
| 3 |
2018-01-11T05:08:54Z
|
2022-09-07T16:37:53Z
|
https://github.com/yasm/yasm/issues/101
| 287,665,731 | 101 |
[
"yasm",
"yasm"
] |
Given `add edx, -9 + 3`, NASM and YASM both assemble it to `83 c2 fa add edx,0xfffffffa`, as expected.
But for `add edx, (1<<32)-9 + 3`, YASM emits `81 c2 fa ff ff ff add edx,0xfffffffa` unless you use `strict byte (1<<32)-9 + 3`. NASM correctly emits `83 c2 fa` in all cases (unless you use `strict dword`). I wrote it this way because I was thinking about unsigned and wanted to set the carry flag by wrapping almost all the way back to where I started, before entering a loop where CF was an input.
It seems YASM does something other than just check whether the low 8 bits will sign extend to the full value. i.e. `(int32_t)imm == (int32_t)(int8_t)imm`. I guess YASM is also "thinking of" the value as large unsigned.
|
Missed optimized of imm32 to imm8 for large unsigned values
|
https://api.github.com/repos/yasm/yasm/issues/100/comments
| 0 |
2017-12-27T23:41:43Z
|
2017-12-27T23:42:24Z
|
https://github.com/yasm/yasm/issues/100
| 284,814,285 | 100 |
[
"yasm",
"yasm"
] |
Hello.
I found a heap-buffer-overflow bug in yasm.
Please confirm.
Thanks.
OS: Ubuntu 16.04 32bit
Version: yasm 1.3.0.36.ge2569
PoC download : [PoC](https://github.com/gy741/PoC/raw/master/handle_dot_label)
Steps to reproduce:
1.Download the .POC files.
2.Compile the source code with ASan.
3. ./yasm $PoC
```
==23008== Invalid read of size 1
==23008== at 0x4EADCE: handle_dot_label (nasm-token.re:82)
==23008== by 0x4E29E1: nasm_parser_lex (nasm-token.re:0)
==23008== by 0x464D34: demand_eol_ (nasm-parse.c:149)
==23008== by 0x464D34: nasm_parser_parse (nasm-parse.c:232)
==23008== by 0x462EF7: nasm_do_parse (nasm-parser.c:66)
==23008== by 0x462EF7: nasm_parser_do_parse (nasm-parser.c:83)
==23008== by 0x403754: do_assemble (yasm.c:521)
==23008== by 0x403754: main (yasm.c:753)
==23008== Address 0x5237c03 is 0 bytes after a block of size 3 alloc'd
==23008== at 0x4C29BE3: malloc (vg_replace_malloc.c:299)
==23008== by 0x447D17: def_xmalloc (xmalloc.c:69)
==23008== by 0x4480BC: yasm__xstrndup (xstrdup.c:64)
==23008== by 0x4EADC5: handle_dot_label (nasm-token.re:79)
==23008== by 0x4E29E1: nasm_parser_lex (nasm-token.re:0)
==23008== by 0x464D34: demand_eol_ (nasm-parse.c:149)
==23008== by 0x464D34: nasm_parser_parse (nasm-parse.c:232)
==23008== by 0x462EF7: nasm_do_parse (nasm-parser.c:66)
==23008== by 0x462EF7: nasm_parser_do_parse (nasm-parser.c:83)
==23008== by 0x403754: do_assemble (yasm.c:521)
==23008== by 0x403754: main (yasm.c:753)
==23008==
```
```
=================================================================
==9128==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000006b73 at pc 0x0000006ce960 bp 0x7ffc6321dd40 sp 0x7ffc6321dd38
READ of size 1 at 0x602000006b73 thread T0
#0 0x6ce95f in handle_dot_label /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:82:13
#1 0x6c223b in nasm_parser_lex /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:384:17
#2 0x5a6e76 in demand_eol_ /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:149:9
#3 0x5a448f in nasm_parser_parse /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:232:13
#4 0x5a3d67 in nasm_do_parse /home/karas/yasm/modules/parsers/nasm/nasm-parser.c:66:5
#5 0x5a36a5 in nasm_parser_do_parse /home/karas/yasm/modules/parsers/nasm/nasm-parser.c:83:5
#6 0x51700e in do_assemble /home/karas/yasm/frontends/yasm/yasm.c:521:5
#7 0x514786 in main /home/karas/yasm/frontends/yasm/yasm.c:753:12
#8 0x7f4167938c04 in __libc_start_main (/lib64/libc.so.6+0x21c04)
#9 0x41af1b in _start (/home/karas/yasm/yasm+0x41af1b)
0x602000006b73 is located 0 bytes to the right of 3-byte region [0x602000006b70,0x602000006b73)
allocated by thread T0 here:
#0 0x4de8b6 in malloc /home/karas/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:66
#1 0x5652e7 in def_xmalloc /home/karas/yasm/libyasm/xmalloc.c:69:14
#2 0x5655ff in yasm__xstrndup /home/karas/yasm/libyasm/xstrdup.c:64:16
#3 0x6ce88f in handle_dot_label /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:79:26
#4 0x6c223b in nasm_parser_lex /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:384:17
#5 0x5a6e76 in demand_eol_ /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:149:9
#6 0x5a448f in nasm_parser_parse /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:232:13
#7 0x5a3d67 in nasm_do_parse /home/karas/yasm/modules/parsers/nasm/nasm-parser.c:66:5
#8 0x5a36a5 in nasm_parser_do_parse /home/karas/yasm/modules/parsers/nasm/nasm-parser.c:83:5
#9 0x51700e in do_assemble /home/karas/yasm/frontends/yasm/yasm.c:521:5
#10 0x514786 in main /home/karas/yasm/frontends/yasm/yasm.c:753:12
#11 0x7f4167938c04 in __libc_start_main (/lib64/libc.so.6+0x21c04)
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:82:13 in handle_dot_label
Shadow bytes around the buggy address:
0x0c047fff8d10: fa fa fd fd fa fa fd fd fa fa fd fd fa fa 00 fa
0x0c047fff8d20: fa fa fd fd fa fa fd fd fa fa fd fd fa fa 04 fa
0x0c047fff8d30: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fa
0x0c047fff8d40: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
0x0c047fff8d50: fa fa 00 07 fa fa fd fd fa fa fd fd fa fa fd fa
=>0x0c047fff8d60: fa fa fd fa fa fa 04 fa fa fa 04 fa fa fa[03]fa
0x0c047fff8d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8d80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8d90: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8da0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c047fff8db0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==9128==ABORTING
```
==========================================
[Acknowledgement]
This work was supported by ICT R&D program of MSIP/IITP. [R7518-16-1001, Innovation hub for high Performance Computing]
|
heap-buffer-overflow in handle_dot_label
|
https://api.github.com/repos/yasm/yasm/issues/99/comments
| 1 |
2017-12-10T12:41:36Z
|
2018-11-12T16:37:24Z
|
https://github.com/yasm/yasm/issues/99
| 280,806,392 | 99 |
[
"yasm",
"yasm"
] |
Hello.
I found a stack-overflow bug in yasm.
Please confirm.
Thanks.
OS: Ubuntu 16.04 32bit
Version: yasm 1.3.0.36.ge2569
PoC download : [PoC](https://github.com/gy741/PoC/raw/master/nasm_parser_lex)
Steps to reproduce:
1.Download the .POC files.
2.Compile the source code with ASan.
3. ./yasm $PoC
```
==43937==
==43937== 56 bytes in 1 blocks are definitely lost in loss record 2 of 2
==43937== at 0x4C29BE3: malloc (vg_replace_malloc.c:299)
==43937== by 0x447D17: def_xmalloc (xmalloc.c:69)
==43937== by 0x4C6FA4: yasm_expr_create (expr.c:69)
==43937== by 0x468744: parse_expr6 (nasm-parse.c:0)
==43937== by 0x46966A: parse_expr5 (nasm-parse.c:1305)
==43937== by 0x4693DD: parse_expr4 (nasm-parse.c:1277)
==43937== by 0x4690CD: parse_expr3 (nasm-parse.c:1249)
==43937== by 0x468EE9: parse_expr2 (nasm-parse.c:1242)
==43937== by 0x468D09: parse_expr1 (nasm-parse.c:1236)
==43937== by 0x467E79: parse_expr0 (nasm-parse.c:1230)
==43937== by 0x467C99: parse_bexpr (nasm-parse.c:1224)
==43937== by 0x467AC1: parse_expr (nasm-parse.c:1215)
==43937==
```
```
ASAN:DEADLYSIGNAL
=================================================================
==32865==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc63488b00 (pc 0x0000006afba0 bp 0x7ffc6348d000 sp 0x7ffc63488b00 T0)
#0 0x6afb9f in nasm_parser_lex /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:117
#1 0x5acdc7 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1400:13
#2 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#3 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#4 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#5 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#6 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#7 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#8 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#9 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#10 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#11 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#12 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#13 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#14 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#15 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#16 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#17 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#18 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#19 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#20 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#21 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#22 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#23 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#24 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#25 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#26 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#27 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#28 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#29 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#30 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#31 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#32 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#33 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#34 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#35 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#36 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#37 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#38 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#39 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#40 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#41 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#42 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#43 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#44 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#45 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#46 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#47 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#48 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#49 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#50 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#51 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#52 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#53 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#54 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#55 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#56 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#57 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#58 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#59 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#60 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#61 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#62 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#63 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#64 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#65 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#66 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#67 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#68 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#69 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#70 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#71 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#72 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#73 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#74 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#75 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#76 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#77 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#78 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#79 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#80 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#81 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#82 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#83 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#84 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#85 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#86 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#87 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#88 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#89 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#90 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#91 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#92 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#93 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#94 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#95 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#96 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#97 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#98 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#99 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#100 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#101 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#102 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#103 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#104 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#105 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#106 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#107 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#108 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#109 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#110 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#111 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#112 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#113 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#114 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#115 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#116 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#117 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#118 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#119 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#120 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#121 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#122 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#123 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#124 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#125 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#126 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#127 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#128 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#129 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#130 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#131 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#132 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#133 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#134 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#135 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#136 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#137 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#138 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#139 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#140 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#141 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#142 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#143 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#144 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#145 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#146 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#147 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#148 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#149 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#150 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#151 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#152 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#153 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#154 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#155 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#156 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#157 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#158 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#159 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#160 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#161 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#162 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#163 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#164 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#165 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#166 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#167 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#168 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#169 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#170 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#171 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#172 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#173 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#174 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#175 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#176 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#177 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#178 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#179 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#180 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#181 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#182 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#183 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#184 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#185 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#186 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#187 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#188 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#189 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#190 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#191 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#192 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#193 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#194 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#195 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#196 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#197 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#198 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#199 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#200 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#201 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#202 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#203 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#204 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#205 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#206 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#207 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#208 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#209 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#210 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#211 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#212 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#213 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#214 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#215 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#216 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#217 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#218 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#219 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#220 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#221 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#222 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#223 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#224 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#225 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#226 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#227 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#228 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#229 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#230 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#231 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#232 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#233 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#234 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#235 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#236 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#237 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#238 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#239 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#240 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#241 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
#242 0x5ac03a in parse_bexpr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1224:5
#243 0x5abbf8 in parse_expr /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1215:13
#244 0x5ace41 in parse_expr6 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1401:17
#245 0x5aeeed in parse_expr5 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1305:9
#246 0x5aeb8d in parse_expr4 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1277:9
#247 0x5ae82d in parse_expr3 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1249:9
#248 0x5ae64a in parse_expr2 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1242:5
#249 0x5ae46a in parse_expr1 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1236:5
#250 0x5ac21a in parse_expr0 /home/karas/yasm/modules/parsers/nasm/nasm-parse.c:1230:5
SUMMARY: AddressSanitizer: stack-overflow /home/karas/yasm/./modules/parsers/nasm/nasm-token.re:117 in nasm_parser_lex
==32865==ABORTING
```
|
stack-overflow in nasm_parser_lex
|
https://api.github.com/repos/yasm/yasm/issues/98/comments
| 0 |
2017-12-10T12:34:24Z
|
2017-12-10T12:34:24Z
|
https://github.com/yasm/yasm/issues/98
| 280,805,950 | 98 |
[
"yasm",
"yasm"
] |
This is either a question and if the answer is "no equivalent" a request for enhancement.
When compiling with `nasm` I used the `%defstr` macro to turn an (unquoted) macro parameter into a string, e.g., so I can define a string constant with that value in `.rodata`. Example:
```
%macro abi_checked_function 1
GLOBAL %1:function
%1:
; some code omitted here
; load the function name (ok to clobber rdi since it's callee-saved)
mov rdi, %1_thunk_fn_name
; here we store strings needed by the failure cases, in the .rodata section
[section .rodata]
%1_thunk_fn_name:
%defstr fname %1
db fname,0
; restore the previous section
__SECT__
%1_inner:
%endmacro
```
Is there any equivalent in in yasm for this pattern?
|
Equivalent to NASM %defstr
|
https://api.github.com/repos/yasm/yasm/issues/95/comments
| 5 |
2017-11-01T05:54:17Z
|
2018-08-18T15:19:37Z
|
https://github.com/yasm/yasm/issues/95
| 270,202,346 | 95 |
[
"yasm",
"yasm"
] |
The attached file will trigger a use after free bug in yasm_intnum_destroy(). This can be detected with address sanitizer, however it'll also crash a normal compile of yasm (glibc detects a double free bug).
[yasm-useafterfree.zip](https://github.com/yasm/yasm/files/1326519/yasm-useafterfree.zip)
This was found with american fuzzy lop.
Here's the asan stack trace:
```
==27027==ERROR: AddressSanitizer: heap-use-after-free on address 0x602000006cd8 at pc 0x00000055f76b bp 0x7ffd82563a70 sp 0x7ffd82563a68
READ of size 4 at 0x602000006cd8 thread T0
#0 0x55f76a in yasm_intnum_destroy /mnt/ram/yasm-1.3.0/libyasm/intnum.c:415:15
#1 0x671164 in expr_delete_term /mnt/ram/yasm-1.3.0/libyasm/expr.c:1017:13
#2 0x671164 in expr_simplify_identity /mnt/ram/yasm-1.3.0/libyasm/expr.c:582
#3 0x668755 in expr_level_op /mnt/ram/yasm-1.3.0/libyasm/expr.c:701:17
#4 0x66b211 in expr_level_tree /mnt/ram/yasm-1.3.0/libyasm/expr.c:880:9
#5 0x66a487 in yasm_expr__level_tree /mnt/ram/yasm-1.3.0/libyasm/expr.c:906:9
#6 0x676492 in yasm_insn_finalize /mnt/ram/yasm-1.3.0/libyasm/insn.c:256:25
#7 0x590bd9 in x86_id_insn_finalize /mnt/ram/yasm-1.3.0/modules/arch/x86/x86id.c:1082:5
#8 0x665843 in yasm_bc_finalize /mnt/ram/yasm-1.3.0/libyasm/bytecode.c:176:9
#9 0x56777b in yasm_object_finalize /mnt/ram/yasm-1.3.0/libyasm/section.c:528:13
#10 0x51591c in do_assemble /mnt/ram/yasm-1.3.0/frontends/yasm/yasm.c:525:5
#11 0x51591c in main /mnt/ram/yasm-1.3.0/frontends/yasm/yasm.c:749
#12 0x7fbef2c1e5bc in __libc_start_main /var/tmp/portage/sys-libs/glibc-2.25-r5/work/glibc-2.25/csu/../csu/libc-start.c:295
#13 0x41a089 in _start (/mnt/ram/yasm-1.3.0/yasm+0x41a089)
0x602000006cd8 is located 8 bytes inside of 16-byte region [0x602000006cd0,0x602000006ce0)
freed by thread T0 here:
#0 0x4db1a0 in __interceptor_cfree.localalias.0 (/mnt/ram/yasm-1.3.0/yasm+0x4db1a0)
#1 0x57d307 in def_xfree /mnt/ram/yasm-1.3.0/libyasm/xmalloc.c:113:5
#2 0x6685fe in expr_level_op /mnt/ram/yasm-1.3.0/libyasm/expr.c:689:17
#3 0x66b211 in expr_level_tree /mnt/ram/yasm-1.3.0/libyasm/expr.c:880:9
#4 0x66a487 in yasm_expr__level_tree /mnt/ram/yasm-1.3.0/libyasm/expr.c:906:9
#5 0x676492 in yasm_insn_finalize /mnt/ram/yasm-1.3.0/libyasm/insn.c:256:25
#6 0x590bd9 in x86_id_insn_finalize /mnt/ram/yasm-1.3.0/modules/arch/x86/x86id.c:1082:5
#7 0x665843 in yasm_bc_finalize /mnt/ram/yasm-1.3.0/libyasm/bytecode.c:176:9
#8 0x56777b in yasm_object_finalize /mnt/ram/yasm-1.3.0/libyasm/section.c:528:13
#9 0x51591c in do_assemble /mnt/ram/yasm-1.3.0/frontends/yasm/yasm.c:525:5
#10 0x51591c in main /mnt/ram/yasm-1.3.0/frontends/yasm/yasm.c:749
#11 0x7fbef2c1e5bc in __libc_start_main /var/tmp/portage/sys-libs/glibc-2.25-r5/work/glibc-2.25/csu/../csu/libc-start.c:295
#12 0x41a089 in _start (/mnt/ram/yasm-1.3.0/yasm+0x41a089)
previously allocated by thread T0 here:
#0 0x4db370 in malloc (/mnt/ram/yasm-1.3.0/yasm+0x4db370)
#1 0x57d0d7 in def_xmalloc /mnt/ram/yasm-1.3.0/libyasm/xmalloc.c:69:14
#2 0x55f511 in yasm_intnum_copy /mnt/ram/yasm-1.3.0/libyasm/intnum.c:397:22
#3 0x66bf5a in expr_item_copy /mnt/ram/yasm-1.3.0/libyasm/expr.c:975:31
#4 0x66aad8 in yasm_expr__copy_except /mnt/ram/yasm-1.3.0/libyasm/expr.c:1006:13
#5 0x66aad8 in expr_expand_equ /mnt/ram/yasm-1.3.0/libyasm/expr.c:834
#6 0x66a467 in yasm_expr__level_tree /mnt/ram/yasm-1.3.0/libyasm/expr.c:905:9
#7 0x676492 in yasm_insn_finalize /mnt/ram/yasm-1.3.0/libyasm/insn.c:256:25
#8 0x590bd9 in x86_id_insn_finalize /mnt/ram/yasm-1.3.0/modules/arch/x86/x86id.c:1082:5
#9 0x665843 in yasm_bc_finalize /mnt/ram/yasm-1.3.0/libyasm/bytecode.c:176:9
#10 0x56777b in yasm_object_finalize /mnt/ram/yasm-1.3.0/libyasm/section.c:528:13
#11 0x51591c in do_assemble /mnt/ram/yasm-1.3.0/frontends/yasm/yasm.c:525:5
#12 0x51591c in main /mnt/ram/yasm-1.3.0/frontends/yasm/yasm.c:749
#13 0x7fbef2c1e5bc in __libc_start_main /var/tmp/portage/sys-libs/glibc-2.25-r5/work/glibc-2.25/csu/../csu/libc-start.c:295
#14 0x41a089 in _start (/mnt/ram/yasm-1.3.0/yasm+0x41a089)
|
use after free with malformed input file in yasm_intnum_destroy()
|
https://api.github.com/repos/yasm/yasm/issues/91/comments
| 0 |
2017-09-23T11:57:32Z
|
2017-09-23T11:57:32Z
|
https://github.com/yasm/yasm/issues/91
| 260,002,960 | 91 |
[
"yasm",
"yasm"
] |
Per 01org/isa-l_crypto#8, it's annoying that GDB can't walk the stack when we're in a function built with yasm. Could you add support for CFI directives to yasm? Or suggest some other way to fix this?
|
Add support for CFI directives.
|
https://api.github.com/repos/yasm/yasm/issues/90/comments
| 4 |
2017-07-27T02:25:15Z
|
2019-02-13T08:37:15Z
|
https://github.com/yasm/yasm/issues/90
| 245,907,779 | 90 |
[
"yasm",
"yasm"
] |
Master-branch commit: 6caf1518939d41627f7d6bb220650f4ce77cd087
OS: Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
Three self-tests fail:
FAIL: modules/arch/x86/tests/x86_test.sh
FAIL: modules/arch/lc3b/tests/lc3b_test.sh
FAIL: libyasm/tests/libyasm_test.sh
[log.txt](https://github.com/yasm/yasm/files/1084300/log.txt)
|
make check - 3 tests faill
|
https://api.github.com/repos/yasm/yasm/issues/89/comments
| 2 |
2017-06-19T08:38:26Z
|
2020-05-03T12:20:33Z
|
https://github.com/yasm/yasm/issues/89
| 236,817,601 | 89 |
[
"yasm",
"yasm"
] |
Hi,
While experimenting with a CodeSonar plugin we develop, we noticed a potential bug in file "asm/modules/dbgfmts/stabs/stabs-dbgfmt.c" line 358 (actually in the chromium project that uses this project as a third-party).
yasm_error_set(YASM_ERROR_GENERAL,
N_("stabs debugging conflicts with user-defined section .stabstr"));
yasm_errwarn_propagate(errwarns,
yasm_section_bcs_first(info.stab)->line); //line 358
Shouldn't you use in line 358 info.stabstr (and not info.stab)?
Thank you.
|
Possible unintended usage of "info.stab" field
|
https://api.github.com/repos/yasm/yasm/issues/88/comments
| 3 |
2017-05-22T16:10:08Z
|
2017-09-29T10:33:52Z
|
https://github.com/yasm/yasm/issues/88
| 230,445,723 | 88 |
[
"yasm",
"yasm"
] |
I've been having some trouble with running make check in my builds of yasm. The hex dumps of various x32 and amd64 outputs were randomly not the same as the reference dumps.
Investigating, they seemed to contain 32-bit elfs when 64-bit elfs were expected and vice versa. I think the problem is that the files in `results/` overwrite each other because only the basename of the full path to the testfile is used to form the `results/filename` yet there are multiple files with the same basename, for example:
```
find . -name "elf-rip.hex"
./modules/objfmts/elf/tests/x32/elf-rip.hex
./modules/objfmts/elf/tests/amd64/elf-rip.hex
```
I could probably knock up a quick fix for this if you were interested, but for now, using `make -j1 check` works. Perhaps this is documented somewhere though and I just missed it? FWIW, in all the projects I've checked, people were not passing `-j1`.
|
make check fails unless run with -j1.
|
https://api.github.com/repos/yasm/yasm/issues/87/comments
| 3 |
2017-04-26T10:55:59Z
|
2017-09-05T09:11:46Z
|
https://github.com/yasm/yasm/issues/87
| 224,426,852 | 87 |
[
"yasm",
"yasm"
] |
Hello,
I want to import global data using ".idata" section but it's not working (win64). Using 'extern' for functions work fine. In short I what something like "__declspec(dllimport)" in assembler. Googling I found other projects like FASM offer this possibility. Is it possible?
Regards,
Happy new year !!
|
Importing global data from external DLL
|
https://api.github.com/repos/yasm/yasm/issues/84/comments
| 0 |
2017-01-09T19:18:28Z
|
2017-01-09T19:18:28Z
|
https://github.com/yasm/yasm/issues/84
| 199,637,899 | 84 |
[
"yasm",
"yasm"
] |
Trying to build https://github.com/freebsd/freebsd/blob/master/sys/crypto/skein/amd64/skein_block_asm.s with yasm segfaults:
% ./yasm -p gas .../sys/crypto/skein/amd64/skein_block_asm.s
zsh: segmentation fault (core dumped) ./yasm -p gas
Host is FreeBSD 10.3, yasm source at 51af4082cc898b122b88f11fd34033fc00fad81e
```
* (lldb) thread #1: tid = 102773, 0x0000000000467188 yasm`yasm_expr_get_intnum(ep=0x00007fffffffd7c8, calc_bc_dist=0) + 84 at expr.c:1377, stop reason = invalid address (fault address: 0x0)
frame #0: 0x0000000000467188 yasm`yasm_expr_get_intnum(ep=0x00007fffffffd7c8, calc_bc_dist=0) + 84 at expr.c:1377
1374 {
1375 *ep = yasm_expr_simplify(*ep, calc_bc_dist);
1376
-> 1377 if ((*ep)->op == YASM_EXPR_IDENT && (*ep)->terms[0].type == YASM_EXPR_INT)
1378 return (*ep)->terms[0].data.intn;
1379 else
1380 return (yasm_intnum *)NULL;
(lldb) bt
* thread #1: tid = 102773, 0x0000000000467188 yasm`yasm_expr_get_intnum(ep=0x00007fffffffd7c8, calc_bc_dist=0) + 84 at expr.c:1377, stop reason = invalid address (fault address: 0x0)
* frame #0: 0x0000000000467188 yasm`yasm_expr_get_intnum(ep=0x00007fffffffd7c8, calc_bc_dist=0) + 84 at expr.c:1377
frame #1: 0x000000000044042f yasm`eval_expr(pp=0x0000000801424020, arg1=0x0000000801415008) + 163 at gas-preproc.c:484
frame #2: 0x000000000044060c yasm`eval_if(pp=0x0000000801424020, negate=0, arg1=0x0000000801415008) + 108 at gas-preproc.c:541
frame #3: 0x0000000000442709 yasm`process_line(pp=0x0000000801424020, line_ptr=0x00007fffffffe038) + 825 at gas-preproc.c:1203
frame #4: 0x0000000000442db2 yasm`gas_preproc_get_line(preproc=0x0000000801424020) + 283 at gas-preproc.c:1336
frame #5: 0x000000000046ed9b yasm`preproc_input(parser_gas=0x00007fffffffe1d0, buf=0x0000000801426000, max_size=7689) + 81 at gas-token.re:64
frame #6: 0x000000000046f144 yasm`fill(parser_gas=0x00007fffffffe1d0, cursor=0x0000000801426000) + 599 at gas-token.re:123
frame #7: 0x000000000046f514 yasm`gas_parser_lex(lvalp=0x00007fffffffe330, parser_gas=0x00007fffffffe1d0) + 279 at gas-token.c:264
frame #8: 0x000000000042abba yasm`gas_parser_parse(parser_gas=0x00007fffffffe1d0) + 578 at gas-parse.c:1742
frame #9: 0x0000000000425f0b yasm`gas_parser_do_parse(object=0x0000000801420080, pp=0x0000000801424020, save_input=0, linemap=0x0000000801413040, errwarns=0x00000008014113e0) + 403 at gas-parser.c:83
frame #10: 0x0000000000402821 yasm`do_assemble + 1819 at yasm.c:521
frame #11: 0x0000000000403084 yasm`main(argc=4, argv=0x00007fffffffe540) + 1486 at yasm.c:752
frame #12: 0x0000000000401abf yasm`_start(ap=<unavailable>, cleanup=<unavailable>) + 367 at crt1.c:72
```
|
gas parser: segfault in yasm_expr_get_intnum()
|
https://api.github.com/repos/yasm/yasm/issues/83/comments
| 0 |
2016-12-27T20:46:17Z
|
2016-12-27T20:46:17Z
|
https://github.com/yasm/yasm/issues/83
| 197,755,639 | 83 |
[
"yasm",
"yasm"
] |
~~~
$ yasm -p gas -o skel.o skel.s
skel.s:3088: error: unexpected end of file in string
$ as -o skel.o skel.s
$ file skel.o
skel.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped
~~~
gas can assemble this, but yasm 1.3.0 with the gas parser fails.
[skel.s](https://github.com/yasm/yasm/files/632372/skel.txt) is attached.
besides this bug, thank you very much for this awesome assembler btw
|
gas parser: "error: unexpected end of file in string" for valid file
|
https://api.github.com/repos/yasm/yasm/issues/82/comments
| 1 |
2016-12-05T21:54:49Z
|
2016-12-06T19:14:49Z
|
https://github.com/yasm/yasm/issues/82
| 193,620,939 | 82 |
[
"yasm",
"yasm"
] |
{{{
If a coder decides to use numeric relative jmps, he should ensure that all
intervening optimizable jmps are specified in size. If he does not, the
optimizer should emit a warning if it changes the size of anything in that
range. Optionally it should emit a warning if it would even be allowed to
change anything in the range, or Error on either case.
Actually i'm tempted to have it default to an error on change, warning on
allowed change.
}}}
|
Warn user when optmizing inside jmp +NN range
|
https://api.github.com/repos/yasm/yasm/issues/58/comments
| 0 |
2011-06-24T16:56:15Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/58
| 1,111,299 | 58 |
[
"yasm",
"yasm"
] |
Greetings,
The Mach-O file format has the N_PEXT bit to limit the global scope as written in 'Mac OS X ABI Mach-O File Format Reference'. It is definitely useful for yasm to have a private extension (such as 'private_extern') that adds the bit as listed in the following example.
{{{
GLOBAL function:private_extern
...
}}}
Regards and thank you for your awesome assembler,
Hironori Bono
|
Add a private extension that adds the N_PEXT bit
|
https://api.github.com/repos/yasm/yasm/issues/57/comments
| 0 |
2011-06-24T16:56:12Z
|
2011-06-24T16:59:28Z
|
https://github.com/yasm/yasm/issues/57
| 1,111,298 | 57 |
[
"yasm",
"yasm"
] |
Help!!!
I'm trying to assemble the simplest program under windows. It should write string to console(using printf procedure from msvcrt.dll) and exit.
Code:
{{{
extern printf
extern ExitProcess
%define exit ExitProcess
section .text
push msg
call printf
push 0
call exit
section .data
msg db 'Hello, world!', 13, 10, 0
}}}
It looks right, I think. Desn't it?
Next I compile it in win32 object file:
'''$ yasm -f win32 hello.asm'''
and this command creates hello.obj file.
Next, I think, I should link it. I'm trying to do it like this:
'''$ ld -o hello.exe hello.obj'''
and I see following:
{{{
hello.obj:hello.asm:(.text+0x6): undefined reference to `printf'
hello.obj:hello.asm:(.text+0xd): undefined reference to`ExitProcess'
}}}
I should say linker that my program takes these procedures from msvcrt.dll and kernel32.dll but I don't know how.. :(
Please, I need help.
PS. Please, don't advise me to use another linkers. I know how to link DLLs with them but I want to use ld only.
PSS. Sorry for my very very bad English :)
|
windows+yasm+cygwin's ld
|
https://api.github.com/repos/yasm/yasm/issues/56/comments
| 0 |
2011-06-24T16:56:09Z
|
2017-02-18T05:22:24Z
|
https://github.com/yasm/yasm/issues/56
| 1,111,296 | 56 |
[
"yasm",
"yasm"
] |
If an input file name is specified without extension, YASM complains about that. Wouldn't it be more appropriate if it just added a default extension .asm, just like it adds a default extension (.obj, .o etc.) in case one did not specify the output name?
|
set default input-file extension to .asm
|
https://api.github.com/repos/yasm/yasm/issues/55/comments
| 0 |
2011-06-24T16:56:06Z
|
2011-06-24T16:56:06Z
|
https://github.com/yasm/yasm/issues/55
| 1,111,295 | 55 |
[
"yasm",
"yasm"
] |
{{{
You cannot concatenate macro arguments like this :
%assign x 0
%rep 8
movd eax,mm(value of x)
push eax
%assign x x+1
%rep
I tried with {, %, %%, labels... I cannot succeed.
Bill's asm can do it and so it is _very_ powerful.
I wrote lots of macros with that feature.
Why not invent a %# (or a %< or an extension of %%...) to give yasm real macro
power...
}}}
|
macros too limited
|
https://api.github.com/repos/yasm/yasm/issues/54/comments
| 0 |
2011-06-24T16:56:03Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/54
| 1,111,294 | 54 |
[
"yasm",
"yasm"
] |
{{{
The "$" operator (current assembly position) cannot be used in expressions for
the %assign directive.
This was seen in YASM version 0.3.0
(Note that your Bugzilla version table dropdown does not list 0.3.0 yet)
For example this fails with "`$' not supported":
%assign ual ($-startseg)
mov eax,ual
But this succeeds:
mov eax,($-startseg)
I've tried this in "-p nasm -r nasm" and also without any -p or -r options.
}}}
|
%assign does not support $
|
https://api.github.com/repos/yasm/yasm/issues/53/comments
| 0 |
2011-06-24T16:56:00Z
|
2011-06-24T16:56:00Z
|
https://github.com/yasm/yasm/issues/53
| 1,111,293 | 53 |
[
"yasm",
"yasm"
] |
When declaring data in the section .data, I sometimes use the built-in macro ALIGNB to ensure proper data alignment. However, I always get the annoying warning message,
{{{
warning: uninitialized space declared in code/data section: zeroing
}}}
Isn't the thing I am getting warned about just what the macro is supposed to be used for?
I cannot see the sense of this warning. Either it should be removed completely, or at least be optional with a switch, say like the warning about orphaned labels.
|
superfluous warning "uninitialized space declared in code/data section..."
|
https://api.github.com/repos/yasm/yasm/issues/52/comments
| 0 |
2011-06-24T16:55:57Z
|
2011-06-24T16:55:57Z
|
https://github.com/yasm/yasm/issues/52
| 1,111,292 | 52 |
[
"yasm",
"yasm"
] |
In order to test, if a condition is not met, currently one has to write: [[BR]]
%if cond = 0[[BR]]
By analogy with the %ifdef / %ifndef pair, it would be nice just to have[[BR]]
%ifn cond[[BR]](or, as in MASM and TASM, %ife cond)[[BR]]
as an abbreviation to the explicit check of cond against 0.
|
request: add %ifn conditional
|
https://api.github.com/repos/yasm/yasm/issues/51/comments
| 0 |
2011-06-24T16:55:54Z
|
2011-06-24T16:55:55Z
|
https://github.com/yasm/yasm/issues/51
| 1,111,291 | 51 |
[
"yasm",
"yasm"
] |
TASM has a very nice feature for those wishing to create whole assembler-written libraries: you can write all input file names into a response file, and TASM will process them one by one. Judging from what I could find in the YASM documentation, there is no comparable feature here. Did I miss it, or is this planned?
|
batch processing
|
https://api.github.com/repos/yasm/yasm/issues/50/comments
| 0 |
2011-06-24T16:55:52Z
|
2011-06-24T16:55:52Z
|
https://github.com/yasm/yasm/issues/50
| 1,111,290 | 50 |
[
"yasm",
"yasm"
] |
mov rax,1[[BR]]
is coded with a 32-bit sign-extended constant. The zero extended form is two bytes shorter.
Note that mov eax,1 is the same as mov rax,1 because of implicit zero-extension.
mov rcx,0xaaaaaaaa[[BR]]
is coded with a full 64-bit constant. The zero-extended version is 5 bytes shorter.
The zero-extended version version is optimal when the constant is in the range[[BR]]
0 <= n < 2^32^.[[BR]]
The sign-extended version is optimal in the range[[BR]]
-2^31^ <= n < 0
|
64-bit move can be made shorter
|
https://api.github.com/repos/yasm/yasm/issues/49/comments
| 1 |
2011-06-24T16:55:49Z
|
2017-08-26T00:23:06Z
|
https://github.com/yasm/yasm/issues/49
| 1,111,289 | 49 |
[
"yasm",
"yasm"
] |
The following command produces a zero length file, while the output should contain the 0xD7 opcode:
echo xlat > test.asm ; yasm -f bin -otest.com test.asm
No errors or warnings are reported.
|
xlat opcode not emitted, instruction dropped silently (0.7.0, 0.7.1)
|
https://api.github.com/repos/yasm/yasm/issues/48/comments
| 0 |
2011-06-24T16:55:46Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/48
| 1,111,288 | 48 |
[
"yasm",
"yasm"
] |
There is currently only one layer of bytecode grouping: sections. For advanced macro support, it's desirable for there to be (at least) one additional middle layer between sections and bytecodes so that a sequence or span of bytecodes can be manipulated as a group.
Things to consider:
- Split data bytecodes with multiple items into multiple bytecodes, and save as a span
- Make a span a type of bytecode? Which leads to...
- Nested spans (traversing might be hard.. basically in-order tree traversal)
- Greater chance of things like circular references?
|
Add bytecode spans/blocks
|
https://api.github.com/repos/yasm/yasm/issues/47/comments
| 0 |
2011-06-24T16:55:44Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/47
| 1,111,286 | 47 |
[
"yasm",
"yasm"
] |
As I was testing the ruby-ffi bindings for libyasm (github.com/sophsec/yasm-ffi), I noticed certain functions were not visible to me.
{{{
$ nm /usr/lib64/libyasm.so | grep yasm_arch
$ nm /usr/lib64/libyasm.so | grep yasm_dv_create_string
$ nm /usr/lib64/libyasm.so | grep yasm_dvs_initialize
$ nm /usr/lib64/libyasm.so | grep yasm_dbgfmt
$ nm /usr/lib64/libyasm.so | grep yasm_error_occurred
$ nm /usr/lib64/libyasm.so | grep yasm_expr_copy
$ nm /usr/lib64/libyasm.so | grep yasm_listfmt
$ nm /usr/lib64/libyasm.so | grep yasm_objfmt
$ nm /usr/lib64/libyasm.so | grep yasm_preproc
$ nm /usr/lib64/libyasm.so | grep yasm_vps_initialize
$ nm /usr/lib64/libyasm.so | grep yasm_vps_append
$ nm /usr/lib64/libyasm.so | grep yasm_vps_first
$ nm /usr/lib64/libyasm.so | grep yasm_vps_next
}}}
Since I wrote the bindings based off of the libyasm documentation, I noticed all of these non-visible functions lacked a YASM_LIB_DECL. Are these functions not supposed to be visible, or is this a minor typo?
|
libyasm.so missing various functions
|
https://api.github.com/repos/yasm/yasm/issues/46/comments
| 0 |
2011-06-24T16:54:58Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/46
| 1,111,282 | 46 |
[
"yasm",
"yasm"
] |
In order for the contents of libyasm.a to be truly relocatable, the object files which make up libyasm.a need to be compiled with the -fPIC option on x86_64 systems.
|
libyasm.a needs to be compiled with -fPIC on x86_64
|
https://api.github.com/repos/yasm/yasm/issues/45/comments
| 0 |
2011-06-24T16:54:51Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/45
| 1,111,281 | 45 |
[
"yasm",
"yasm"
] |
I compiled and installed yasm-0.8.0 from source on my Fedora Core 10 system, and noticed that libyasm.a was installed. While having libyasm.a is useful for compiling programs against yasm, I need libyasm.so in order to write dynamic bindings for Ruby (using libffi and ruby-ffi which dynamically links against libyasm.so at runtime).
Could the build system be modified to also produce a libyasm.so file?
|
yasm should create libyasm.so along with libyasm.a
|
https://api.github.com/repos/yasm/yasm/issues/44/comments
| 0 |
2011-06-24T16:54:42Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/44
| 1,111,279 | 44 |
[
"yasm",
"yasm"
] |
Please add disassembler support (like ndisasm) with the amd64 extension support.
|
Disassembler
|
https://api.github.com/repos/yasm/yasm/issues/43/comments
| 0 |
2011-06-24T16:54:39Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/43
| 1,111,278 | 43 |
[
"yasm",
"yasm"
] |
Add support for PowerPC family of processors.
|
Support for PowerPC Architecture
|
https://api.github.com/repos/yasm/yasm/issues/42/comments
| 0 |
2011-06-24T16:54:36Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/42
| 1,111,277 | 42 |
[
"yasm",
"yasm"
] |
Need support for OMF 16-bit and 32-bit object file creation.
|
OMF Object Format Support
|
https://api.github.com/repos/yasm/yasm/issues/41/comments
| 0 |
2011-06-24T16:54:33Z
|
2011-06-24T21:12:12Z
|
https://github.com/yasm/yasm/issues/41
| 1,111,275 | 41 |
[
"yasm",
"yasm"
] |
For FFMPEG, I need yasm and it runs a configure script that
checks for yasm. This fails for the latest 32-bit or 64-bit
"general" yasm exes that are provided for download. I traced
the problem down to yasm not interpreting paths properly that
start /cygdrive/c/...; it wants a windows style path c:\
Back in 0.8.0, you provided a special cygwin exe download.
Why is this variant no longer offered? I looked at the command
line options for yasm and their is no "enable cygwin paths" option.
|
Cygwin paths don't work in 32-bit or 64-bit current release of Yasm
|
https://api.github.com/repos/yasm/yasm/issues/40/comments
| 0 |
2011-06-24T16:54:29Z
|
2011-06-24T16:54:29Z
|
https://github.com/yasm/yasm/issues/40
| 1,111,274 | 40 |
[
"yasm",
"yasm"
] |
With the version got from git and compiled with MSVC
yasm 1.1.99.HEAD
Compiled on Apr 4 2011.
the following inst:
xor rax,0FFFFFFFFFFFFFFF0h
emits a warning 'value does not fit in 32 bit field'.
This is also true for and, or.
No warning should be emitted here.
Daniel
|
x86_64 xor/and/or warns about constant expressions exceeding 32-bits
|
https://api.github.com/repos/yasm/yasm/issues/39/comments
| 1 |
2011-06-24T16:54:26Z
|
2017-08-26T00:35:28Z
|
https://github.com/yasm/yasm/issues/39
| 1,111,273 | 39 |
[
"yasm",
"yasm"
] |
getting the latest git repo and running autogen configure make make check to get this
h
Test nasmpp_test: .......... +10-0/10 100%
PASS: modules/preprocs/nasm/tests/nasmpp_test.sh
Test rawpp_test: . +1-0/1 100%
PASS: modules/preprocs/raw/tests/rawpp_test.sh
Test dwarf2_gen64_test: O +0-1/1 0%
*\* O: dwarf64_pathname did not match object file!
FAIL: modules/dbgfmts/dwarf2/tests/gen64/dwarf2_gen64_test.sh
Test dwarf2_pass32_test: .. +2-0/2 100%
PASS: modules/dbgfmts/dwarf2/tests/pass32/dwarf2_pass32_test.sh
Test dwarf2_pass64_test: .. +2-0/2 100%
this is with gcc-4.4.4 automake 1.11.1 autoconf 2.68 libtool 2.4 on linux 64 bit
|
make check failure
|
https://api.github.com/repos/yasm/yasm/issues/38/comments
| 0 |
2011-06-24T16:54:23Z
|
2011-06-24T16:54:23Z
|
https://github.com/yasm/yasm/issues/38
| 1,111,272 | 38 |
[
"yasm",
"yasm"
] |
source files which describe the problem are attached
|
no local relocation generated for macho64 target when [wrt rip] used
|
https://api.github.com/repos/yasm/yasm/issues/37/comments
| 0 |
2011-06-24T16:54:19Z
|
2011-06-24T16:54:19Z
|
https://github.com/yasm/yasm/issues/37
| 1,111,271 | 37 |
[
"yasm",
"yasm"
] |
In the shl, shr, sal, sar commands, the count is normally masked to 5 bits, i.e., it is limited to a number between 0 and 31. This is true also for the 64-bit registers. Only with a REX.W prefix, the full range of 0..63 can be used. This REX prefix seems not to be emitted by YASM, as the line
{{{
shl rax, 32
}}}
just performs nothing (showing that the bit masking changes the immediate 32 into 0).
|
REX prefix missing in shl
|
https://api.github.com/repos/yasm/yasm/issues/36/comments
| 1 |
2011-06-24T16:54:15Z
|
2017-08-26T00:38:27Z
|
https://github.com/yasm/yasm/issues/36
| 1,111,269 | 36 |
[
"yasm",
"yasm"
] |
The zip file for the 1.1.0 win32 Visual Studio 2010 integration contains invalid references to c:\program files (x86).... as the location for the yasm and visual studio installs. This path is correct for Win64, but not for win32. It should be c:\program files... or $ProgramFiles or %program files% so that it will match if c: is not the main drive.
To fix, just remove " (x86)" from the .prop and the readme file for the vs2010 win32 zip file.
|
Win32 VS2010 contain incorrect pathing for yasm executable in .prop and readme file
|
https://api.github.com/repos/yasm/yasm/issues/35/comments
| 0 |
2011-06-24T16:54:12Z
|
2011-06-24T16:54:12Z
|
https://github.com/yasm/yasm/issues/35
| 1,111,267 | 35 |
[
"yasm",
"yasm"
] |
Using DWARF2 debug information in 64 bit Windows object files causes the Microsoft linker shipped with Visual Studio 2008 (and later) to throw 'ADDR32' relocation invalid errors.
I can provide a .s file that contains the small amount of DWARF information needed to reproduce the error but here are the basics. The relocations that generate the errors are the 4 byte links between the DWARF2 sections, .debug_info to .debug_abbrev, .debug_info to .debug_line, etc.
In the assembly source (for example):
.section .debug_info
.byte 0x82, 0x00, 0x00, 0x00, 0x02, 0x00
.4byte .debug_abbrev
assembled into:
Offset Type Applied To Index Name[[BR]]
-------- ---------------- ----------------- -------- ------[[BR]]
00000006 ADDR32 00000000 C .debug_abbrev[[BR]]
For this relocation, the Microsoft linker reports
1>t.obj : error LNK2017: 'ADDR32' relocation to '.debug_abbrev' invalid without /LARGEADDRESSAWARE:NO
Obviously, using /LARGEADDRESSAWARE:NO is useless for a 64 bit object file. There is an assumption that the total size of DWARF2 information will not exceed 2 gigabytes but there does not seem to be a way to get the Microsoft linker to accept this and I am not sure there is a solution short of generating full 64 bit DWARF3 information.
Would the IMAGE_REL_AMD64_SECREL (32-bit offset of the target from the beginning of its section) be a valid replacement for the current IMAGE_REL_AMD64_ADDR32 relocation?
|
Invalid relocations for 32 bit DWARF2 in 64 bit Windows object files
|
https://api.github.com/repos/yasm/yasm/issues/34/comments
| 0 |
2011-06-24T16:53:43Z
|
2011-06-24T16:53:43Z
|
https://github.com/yasm/yasm/issues/34
| 1,111,264 | 34 |
[
"yasm",
"yasm"
] |
yasm refuses to assemble this code (on an i386 box):
pabsw xmm0, xmm0
{{{
$ yasm -f elf -DARCH_X86_32 -g dwarf2 -o /tmp/ffconf.wBH20568.o /tmp/ffconf.uLd20570.S
/tmp/ffconf.uLd20570.S:1: label or instruction expected at start of line
}}}
This error occurs in the ffmpeg configure script.
Just for lulz, I tried this too:
{{{
$ yasm -p gas /tmp/foo.S
/tmp/foo.S:1: instruction not recognized: `pabsw'
}}}
|
bogus "label or instruction expected at start of line" error
|
https://api.github.com/repos/yasm/yasm/issues/33/comments
| 0 |
2011-06-24T16:53:40Z
|
2011-06-24T16:53:40Z
|
https://github.com/yasm/yasm/issues/33
| 1,111,263 | 33 |
[
"yasm",
"yasm"
] |
In order to write large blocks of nearly repeating code, I rely on macros with %rep blocks. It turns out that the code quality, as measured by execution speed, deteriorates, if there are more than 5 macro parameters. Consider the following example:
{{{
%macro CopyComplexToBlock 8
%define k_DestReg %1
%define k_SrcReg %2
%define k_BlockHtW %3
%define k_SrcLenW %4
%define k_cx %5
%assign W %6
%assign k_BlockLen %7
%assign k_bias %8
; code part of macro....
}}}
This macro would have to be called like:
{{{
CopyComplexToBlock rdi, rsi, r8, r9, rcx, 4, 48, 128
}}}
Without any modification of the code part of this macro, execution is more than 10% faster, if only the numerical constants (which are %assigned rather than %defined) are moved out of the macro header:
{{{
%macro CopyComplexToBlock 5
%define k_DestReg %1
%define k_SrcReg %2
%define k_BlockHtW %3
%define k_SrcLenW %4
%define k_cx %5
; exactly the same macro code part as above...
}}}
This form of the macro would have to be called like:
{{{
%assign W 4
%assign k_BlockLen 48
%assign k_bias 128
CopyComplexToBlock rdi, rsi, r8, r9, rcx
}}}
Instead of one line, I need four lines, but the code executes considerably faster! [[BR]]
Here is the actual code, following after the header:
{{{
mov k_cx, k_BlockHtW
ALIGN 16
%%CopyComplexToBlockNextRow:
%assign k_off -k_bias
%rep (k_BlockLen_W) / 8
wmovupf xmm0, [k_SrcReg+k_off], W
wmovupf xmm1, [k_SrcReg+k_off+xmmSize], W
wmovupf xmm2, [k_SrcReg+k_off+2_xmmSize], W
wmovupf xmm3, [k_SrcReg+k_off+3_xmmSize], W
wmovapf xmm4, xmm0, W
wshufpf xmm0, xmm1, 10001000b, W
wmovapf xmm5, xmm2, W
wshufpf xmm2, xmm3, 10001000b, W
wshufpf xmm4, xmm1, 11011101b, W
wmovapf [k_DestReg+k_off], xmm0, W
wshufpf xmm5, xmm3, 11011101b, W
wmovapf [k_DestReg+k_off+2_xmmSize], xmm2, W
wmovapf [k_DestReg+k_off+xmmSize], xmm4, W
wmovapf [k_DestReg+k_off+3_xmmSize], xmm5, W
%endrep
add k_SrcReg, k_SrcLenW
add k_DestReg, k_BlockLen_W
sub k_cx, 2*W
jnz %%CopyComplexToBlockNextRow
%endmacro
}}}
In a separate macro definition file, the command wmovapf is translated into movaps, movapd, vmovaps, or vmovapd, depending on the choice of target processor and single or double data, as selected by the parameter W. Same procedure for wmovupf and wshufpf.
[[BR]]
I am not sure where to locate the problem. My best guess would be that the preprocessor just gets confused with too many macro arguments. On the other hand, 8 arguments is not that many and should not drive the assembler into difficulties.
|
Code quality deteriorates for macros with > 5 arguments
|
https://api.github.com/repos/yasm/yasm/issues/32/comments
| 1 |
2011-06-24T16:53:38Z
|
2017-08-26T00:43:38Z
|
https://github.com/yasm/yasm/issues/32
| 1,111,262 | 32 |
[
"yasm",
"yasm"
] |
cython.m4 is unable to understand Cython 0.13 installation because it can't parse the version string.
Skipping the check allows yasm-1.1.0 to compile & work succesfully with Cython-0.13_beta0.
configure:8067: checking for Cython >= 0.11.3
configure:8080: /usr/bin/python -c import sys from Cython.Compiler.Version import version # split
strings by '.' and convert to numeric. Append some zeros # because we need at least 4 digits for
the hex conversion. ver = map(int, version.rstrip('abcdefghijklmnopqrstuvwxyz').split('.')) + [0
, 0, 0] verhex = 0 for i in xrange(0, 4): verhex = (verhex << 8) + ver[i] minver = map(int, '0.11
.3'.split('.')) + [0, 0, 0] minverhex = 0 for i in xrange(0, 4): minverhex = (minverhex << 8) + m
inver[i] sys.exit(verhex < minverhex)
Traceback (most recent call last):
File "<string>", line 5, in <module>
ValueError: invalid literal for int() with base 10: 'beta0'
|
yasm-1.1.0 m4/cython.m4 macro is broken for Cython 0.13 "beta0"
|
https://api.github.com/repos/yasm/yasm/issues/31/comments
| 0 |
2011-06-24T16:53:35Z
|
2011-06-24T16:53:35Z
|
https://github.com/yasm/yasm/issues/31
| 1,111,261 | 31 |
[
"yasm",
"yasm"
] |
If somewhere in the depths of code there is an orphaned %endif, YASM correctly complains about that. However, it does not give the line number, where this %endif was encountered. This is the actual message I get:[[BR]]
yasm: FATAL: `%endif': no matching`%if'[[BR]]
Sometimes, this omission of the line-number information makes it very hard to locate the mistake.
|
Orphaned-%endif error reported without line number
|
https://api.github.com/repos/yasm/yasm/issues/30/comments
| 0 |
2011-06-24T16:53:32Z
|
2011-06-24T16:53:32Z
|
https://github.com/yasm/yasm/issues/30
| 1,111,260 | 30 |
[
"yasm",
"yasm"
] |
I have a number of observations and wishes concerning list files:
1. If an error occurs during assembling, no list file is generated, even if requested. This is very impractical, as a list file appears to be the best way to track errors in macros: An error inside a macro is reported for the calling code line of the assembled file. Sometimes, the macro name and line is indicated as well. More often, however, this information is missing. In order to track down errors in larger macros, this additional information would be highly appreciated!
2. There should me an option like .list_conditionals to show the line
%if <conditional>
before the following code. Right now, only line numbers are given, and it is possible only by comparing the source code with the list file to find out which branch has been taken.
Additionally, in conjunction with "wish #1", one could easily track down an %if / %else / %endif mismatch.
3. For error analysis in macros, it would be good to be able to show %assign statements in the list file, let's say by having an option .list_assign.
4. Values in %if, %define, EQU statements are listed as the sometimes rather complex expressions they are defined as. It would be nice to have the actual value added in braces afterwards.
I would suggest braces, because both normal and square brackets already have specific meanings.
E.g., the statement
Next64Byte EQU ((-64) >> lbWW)
is cited in the list file just like that (lbWW is a constant defined somewhere else by an EQU statement to be equal to 2). It could be very valuable to have this line read instead:
Next64Byte EQU ((-64) >> lbWW {2}) {-16}
Likewise, if by a series of previous conditional EQU statements, the constants A,B,C,D are assigned values, the following list file line could be generated:
%if (A+B+C) > D
In order to track down a suspected problem arising from this expression, one would have to search the list file for the valid EQU statements of each of the constants, then add them up manually and evaluate the expression. The list file could greatly simplify that tastk by writing:
%if (A+B+C) > 2_D {(3066+4077+5088) {12231} > 2_5011 {10022}): TRUE}
As you can see from this example, to be useful, the braces would have to be nested whenever the %if condition consists of an arithmetic comparison of parameters to be evaluated by the parser.
1. The list file sometimes contains a lot of unnecessary white space and line number information.
Consider the following situation:
In the included file cb.a, I define a number of macros. In the list file, I can read then:
38 %line 7+1 cb.a
39
40 %line 13+1 cb.a
41
42 %line 19+1 cb.a
43
44 %line 40+1 cb.a
45
46 %line 71+1 cb.a
47
48 %line 88+1 cb.a
49
50 %line 105+1 cb.a
51
52 %line 146+1 cb.a
It does not make a difference here, if the macros contain the .nolist specifier or not. Now, this is no useful information and should just be left away.
|
list file wishes
|
https://api.github.com/repos/yasm/yasm/issues/29/comments
| 0 |
2011-06-24T16:53:30Z
|
2011-06-24T16:53:30Z
|
https://github.com/yasm/yasm/issues/29
| 1,111,259 | 29 |
[
"yasm",
"yasm"
] |
It'd be nice if YASM allowed the user to define an instruction-set to use, sort of like TASM. This way, I would be able to use NASM's impressive macro support with nonstandard processors, like CHIP-8, without having to use any shareware programs.
It'd sure be a lot more efficient than defining a macro for every single instruction I want to support...
|
User definable instruction-set
|
https://api.github.com/repos/yasm/yasm/issues/28/comments
| 0 |
2011-06-24T16:53:27Z
|
2011-06-24T16:53:27Z
|
https://github.com/yasm/yasm/issues/28
| 1,111,258 | 28 |
[
"yasm",
"yasm"
] |
The Borland / Embarcadero compilers (C++ Builder, RAD Studio, Delphi) require external libraries or .obj files to be in the OMF format.
Any plans to add OMF output format support to YASM?
|
OMF format support?
|
https://api.github.com/repos/yasm/yasm/issues/27/comments
| 1 |
2011-06-24T16:53:25Z
|
2017-09-29T19:18:41Z
|
https://github.com/yasm/yasm/issues/27
| 1,111,257 | 27 |
[
"yasm",
"yasm"
] |
It would be nice to have support for macho debug symbols so that gdb can be used do debug yasm
|
yasm support for debug symbols for macho
|
https://api.github.com/repos/yasm/yasm/issues/26/comments
| 2 |
2011-06-24T16:53:22Z
|
2016-10-14T01:04:45Z
|
https://github.com/yasm/yasm/issues/26
| 1,111,256 | 26 |
[
"yasm",
"yasm"
] |
./Configure
make -j 8 fails on Vista32 Cygwin
min/yasm-0.8.0
{{{
$ ./configure && make -j 8
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu
99
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for xmlto... no
configure: WARNING: xmlto not found, manpages will not be rebuilt.
checking if malloc debugging is wanted... no
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for strings.h... (cached) yes
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking for unistd.h... (cached) yes
checking direct.h usability... no
checking direct.h presence... no
checking for direct.h... no
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for function prototypes... yes
checking for size_t... yes
checking for stdint types... stdint.h (shortcircuit)
make use of stdint.h in libyasm-stdint.h (assuming C99 compatible system)
checking for abort... yes
checking for toascii... yes
checking for vsnprintf... yes
checking for strsep... yes
checking for mergesort... no
checking for getcwd... yes
checking for popen... yes
checking for ftruncate... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for stricmp... no
checking for _stricmp... no
checking for strcmpi... no
checking whether NLS is requested... yes
checking for msgfmt... no
checking for gmsgfmt... :
checking for xgettext... no
checking for msgmerge... no
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for ld used by GCC... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... no
checking for iconv... no, consider installing GNU libiconv
checking for GNU gettext in libintl... no
checking whether to use NLS... no
checking for GNU C Library... no
configure: Checking for Python
checking for a Python interpreter with version >= 2.4... none
configure: WARNING: Python not found
configure: WARNING: Could not find a suitable version of Python
configure: creating ./config.status
config.status: creating Makefile
config.status: creating po/Makefile.in
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libyasm-stdint.h commands
config.status: creating libyasm-stdint.h : _YASM_LIBYASM_STDINT_H
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
make: Circular x86insn_nasm.gperf <- x86insn_nasm.gperf dependency dropped.
make: Circular x86insn_gas.gperf <- x86insn_gas.gperf dependency dropped.
gcc -std=gnu99 -I. -c -o genperf.o `test -f tools/genperf/genperf.c || echo './
'`tools/genperf/genperf.c
gcc -std=gnu99 -I. -c -o gp-perfect.o `test -f tools/genperf/perfect.c || echo
'./'`tools/genperf/perfect.c
gcc -std=gnu99 -I. -c -o gp-phash.o `test -f libyasm/phash.c || echo './'`libya
sm/phash.c
gcc -std=gnu99 -I. -c -o gp-xmalloc.o `test -f libyasm/xmalloc.c || echo './'`l
ibyasm/xmalloc.c
gcc -std=gnu99 -I. -c -o gp-xstrdup.o `test -f libyasm/xstrdup.c || echo './'`l
ibyasm/xstrdup.c
gcc -std=gnu99 -I. -c -o re2c-main.o `test -f tools/re2c/main.c || echo './'`to
ols/re2c/main.c
gcc -std=gnu99 -I. -c -o re2c-code.o `test -f tools/re2c/code.c || echo './'`to
ols/re2c/code.c
gcc -std=gnu99 -I. -c -o re2c-dfa.o `test -f tools/re2c/dfa.c || echo './'`tool
s/re2c/dfa.c
gcc -std=gnu99 -I. -c -o re2c-parser.o `test -f tools/re2c/parser.c || echo './
'`tools/re2c/parser.c
gcc -std=gnu99 -I. -c -o re2c-actions.o `test -f tools/re2c/actions.c || echo '
./'`tools/re2c/actions.c
gcc -std=gnu99 -I. -c -o re2c-scanner.o `test -f tools/re2c/scanner.c || echo '
./'`tools/re2c/scanner.c
gcc -std=gnu99 -I. -c -o re2c-mbo_getopt.o `test -f tools/re2c/mbo_getopt.c ||
echo './'`tools/re2c/mbo_getopt.c
gcc -std=gnu99 -I. -c -o re2c-substr.o `test -f tools/re2c/substr.c || echo './
'`tools/re2c/substr.c
gcc -std=gnu99 -I. -c -o re2c-translate.o `test -f tools/re2c/translate.c || ec
ho './'`tools/re2c/translate.c
gcc -std=gnu99 -I. -c -o genmacro.o `test -f tools/genmacro/genmacro.c || echo
'./'`tools/genmacro/genmacro.c
gcc -std=gnu99 -I. -c -o genversion.o `test -f modules/preprocs/nasm/genversion
.c || echo './'`modules/preprocs/nasm/genversion.c
gcc -std=gnu99 -I. -c -o genstring.o `test -f genstring.c || echo './'`genstrin
g.c
gcc -std=gnu99 -o genperf.exe genperf.o gp-perfect.o gp-phash.o gp-xmalloc.o gp
-xstrdup.o
gcc -std=gnu99 -o re2c.exe re2c-main.o re2c-code.o re2c-dfa.o re2c-parser.o re2
c-actions.o re2c-scanner.o re2c-mbo_getopt.o re2c-substr.o re2c-translate.o
gcc -std=gnu99 -o genmacro.exe genmacro.o
gcc -std=gnu99 -o genversion.exe genversion.o
./genperf.exe x86insn_nasm.gperf x86insn_nasm.c
./genperf.exe x86insn_gas.gperf x86insn_gas.c
./re2c.exe -b -o gas-token.c ./modules/parsers/gas/gas-token.re
./re2c.exe -b -o nasm-token.c ./modules/parsers/nasm/nasm-token.re
./genmacro.exe nasm-macros.c nasm_standard_mac ./modules/parsers/nasm/nasm-std.m
ac
./genversion.exe version.mac
./genmacro.exe win64-nasm.c win64_nasm_stdmac ./modules/objfmts/coff/win64-nasm.
mac
gcc -std=gnu99 -o genstring.exe genstring.o
found distinct (A,B) on attempt 19
built perfect hash table of size 512
./genmacro.exe win64-gas.c win64_gas_stdmac ./modules/objfmts/coff/win64-gas.mac
```
3 [main] re2c 5616 _cygtls::handle_exceptions: Error while dumping state (
```
probably corrupted stack)
found distinct (A,B) on attempt 349make
**\* [gas-token.c] Segmentation fault (core dumped)
make: **\* Deleting file `gas-token.c'
make: **\* Waiting for unfinished jobs....
built perfect hash table of size 512
}}}
Parallel make works fine on mingw/linux/solaris
|
Parallel make fails on Cygwin
|
https://api.github.com/repos/yasm/yasm/issues/25/comments
| 0 |
2011-06-24T16:53:19Z
|
2011-06-24T16:53:19Z
|
https://github.com/yasm/yasm/issues/25
| 1,111,255 | 25 |
[
"yasm",
"yasm"
] |
{{{
~> cat foo.asm
%define foo f %+ oo
foo
~> yasm foo.asm
<hangs>
}}}
|
infinite loop in recursive define
|
https://api.github.com/repos/yasm/yasm/issues/24/comments
| 0 |
2011-06-24T16:53:16Z
|
2011-06-24T16:53:16Z
|
https://github.com/yasm/yasm/issues/24
| 1,111,254 | 24 |
[
"yasm",
"yasm"
] |
In order to do easy porting from SSE to AVX.
What do you think about feature, that generate AVX code by SSE instructions
For example
addpd xmm1, xmm2 should be encoded as vaddpd xmm1,xmm1,xmm2
addpd xmm1, <mem> should be encoded as vaddpd xmm1,xmm1,<mem>
|
Encode SSE instructions as AVX
|
https://api.github.com/repos/yasm/yasm/issues/23/comments
| 0 |
2011-06-24T16:53:13Z
|
2011-06-24T16:53:13Z
|
https://github.com/yasm/yasm/issues/23
| 1,111,253 | 23 |
[
"yasm",
"yasm"
] |
Code:
org 1
_label:
mov ax, (_label << 10)
Actual result:
% yasm -f bin test.asm
test.asm:3: error: immediate expression too complex
% nasm -f bin test.asm
test.asm:3: error: shift operator may only be applied to scalar values
Expected result:
% sed 's/<</shl/' -i test.asm && fasm test.asm
1 passes, 3 bytes.
|
Full arithmetic on labels when using non-relocatable formats.
|
https://api.github.com/repos/yasm/yasm/issues/22/comments
| 0 |
2011-06-24T16:50:46Z
|
2011-06-24T16:50:46Z
|
https://github.com/yasm/yasm/issues/22
| 1,111,240 | 22 |
[
"yasm",
"yasm"
] |
GAS-parser is not recognize a lot of keywords used for macroses:
warning: directive `.altmacro' not recognized
warning: directive `.intel_syntax' not recognized
warning: directive `.arch' not recognized
warning: directive `.macro' not recognized
warning: directive `.endm' not recognized
warning: directive `.ifc' not recognized
warning: directive `.endif' not recognized
error: instruction not recognized: `local'
(local vars)
Tested on yasm v0.7.2
|
GAS-parser is not recognize a lot of keywords used for macroses
|
https://api.github.com/repos/yasm/yasm/issues/21/comments
| 0 |
2011-06-24T16:50:43Z
|
2011-06-24T16:50:43Z
|
https://github.com/yasm/yasm/issues/21
| 1,111,239 | 21 |
[
"yasm",
"yasm"
] |
Is it possible to specify the properties of a segment, such as alignment, writeable, executable, zerofill?
I am considering to add support for YASM syntax in my disassembler, www.agner.org/optimize/objconv.zip but I need these features.
|
Segment alignment etc.
|
https://api.github.com/repos/yasm/yasm/issues/20/comments
| 0 |
2011-06-24T16:50:41Z
|
2011-06-24T16:50:41Z
|
https://github.com/yasm/yasm/issues/20
| 1,111,237 | 20 |
[
"yasm",
"yasm"
] |
do you have any documentation on the gas syntax? esp that which is outputted from gcc? thanks very much
|
gas syntax
|
https://api.github.com/repos/yasm/yasm/issues/19/comments
| 0 |
2011-06-24T16:50:38Z
|
2011-06-24T16:50:38Z
|
https://github.com/yasm/yasm/issues/19
| 1,111,236 | 19 |
[
"yasm",
"yasm"
] |
Hi,
If I want to compose Win64/x64 UNWIND_INFO structure myself and register custom language-specific exception [or termination] handler of own design, I'd have to
{{{
section .text
handler: ret
func: ret
func_end:
section .pdata
dd func
dd func_end
dd myunwnd
section .xdata rdata align=8 nobase
myuwnd: db 9,0,0,0
dd handler
}}}
I.e. nobase relocation is a must for handler. Now, rdata and align=8 are default and silently enforced, so I can omit them. But then one can argue that nobase should be enforced by default. But UNWIND_INFO can be followed by user-defined data and one can as well argue that some would like to reserve for nobase relocations there. In which case, if choice of nobase attribute for .xdata is left to developer, there should be a way to selectively generate nobase relocations. Possible suggestion is 'wrt ..imagebase' [suggested to nasm along with patch].
To summarize. If there is no way to selectively generate nobase relocations (e.g. with 'wrt ..imagebase'), then it's natural to enforce nobase on .xdata section (which should be explicitly documented so that developers know that nobase relocations is the only option if they want to append handler-specific data to UNWIND_INFO). A.
|
win64 .xdata section defaults
|
https://api.github.com/repos/yasm/yasm/issues/18/comments
| 0 |
2011-06-24T16:50:35Z
|
2011-06-24T16:50:35Z
|
https://github.com/yasm/yasm/issues/18
| 1,111,235 | 18 |
[
"yasm",
"yasm"
] |
came across this bit of code:
{{{
section .data
contextbegin:
_fetch dd 0
_readbyte dd 0
_readword dd 0
contextend:
section .text
%rep ((contextend-contextbegin) / 8)
mov eax,[contextbegin]
%endrep
}}}
yasm aborts with:
{{{
test.asm:8: cannot reference symbol `contextend' in preprocessor
test.asm:8: cannot reference symbol`contextbegin' in preprocessor
}}}
which i would understand if we were trying to utilize the value of the symbol directly ... but here we're using unknown values with a known difference. so while the address of contextend and contextbegin may not be known at preproccessing time, the difference in their addresses is known.
|
unable to use differences in labels in preprocessor code
|
https://api.github.com/repos/yasm/yasm/issues/17/comments
| 0 |
2011-06-24T16:50:33Z
|
2011-06-24T16:50:33Z
|
https://github.com/yasm/yasm/issues/17
| 1,111,234 | 17 |
[
"yasm",
"yasm"
] |
It would be helpful if yasm could produce sourcecode-line references into the -g debugging output, so that the assembler program can be debugged with KDBG more easily.
|
better debugging support
|
https://api.github.com/repos/yasm/yasm/issues/16/comments
| 0 |
2011-06-24T16:50:31Z
|
2011-06-24T16:50:31Z
|
https://github.com/yasm/yasm/issues/16
| 1,111,233 | 16 |
[
"yasm",
"yasm"
] |
Skimmed through first chapter of Nasm syntax manual starting at
http://www.tortall.net/projects/yasm/manual/html/nasm.html and
somebody has forgotten to state the most obvious fact of the
instruction format:
Does
mov eax,ebx
refer to
mov eax<-ebx
or
mov eax->ebx
???
Explanation to this should be the very first thing in the manual.
|
Manual clarification for Nasm syntax
|
https://api.github.com/repos/yasm/yasm/issues/15/comments
| 0 |
2011-06-24T16:50:28Z
|
2011-06-24T16:50:28Z
|
https://github.com/yasm/yasm/issues/15
| 1,111,232 | 15 |
[
"yasm",
"yasm"
] |
{{{
Debug\SegmentUtils.s:9: warning: directive `.def' not recognized
Debug\SegmentUtils.s:9: warning: directive`.scl' not recognized
Debug\SegmentUtils.s:9: label or instruction expected at start of line
}}}
|
error while assembling gcc output
|
https://api.github.com/repos/yasm/yasm/issues/14/comments
| 0 |
2011-06-24T16:50:25Z
|
2011-06-24T16:50:25Z
|
https://github.com/yasm/yasm/issues/14
| 1,111,231 | 14 |
[
"yasm",
"yasm"
] |
When yasm_bc_tobytes does more than one iteration in for loop (i in {0...bc->mult_int}) there is no way the offset parameter of output_value calls can be right. This affects fixup generation of elf and possible other targets.
I've hacked up a very unrealistic example of how to reproduce the issue (I've got another one for OMF but that depends on unfinished code):
- tst-value-offset-elf64.asm:
{{{
section .data
foobar:
dq 42
section .text
foo:
times 4 mov rax, [foobar wrt rip]
}}}
- Assemble the file as elf64.
- Use objdump to disassemble and dump relocations:
{{{
tst-value-offset-elf64.o: file format elf64-little
SYMBOL TABLE:
0000000000000000 l df _ABS_ 0000000000000000 tst-value-offset-elf64.asm
0000000000000000 l .text 0000000000000000
0000000000000000 l .data 0000000000000000
0000000000000000 l d .data 0000000000000000 .data
0000000000000000 l d .text 0000000000000000 .text
Disassembly of section .text:
0000000000000000 <.text>:
0: 48 8b 05 00 00 00 00 mov 0x0(%rip),%rax # 0x7
3: UNKNOWN .data+0xfffffffffffffffc
3: UNKNOWN .data+0xfffffffffffffff5
3: UNKNOWN .data+0xffffffffffffffee
3: UNKNOWN .data+0xffffffffffffffe7
7: 48 8b 05 00 00 00 00 mov 0x0(%rip),%rax # 0xe
e: 48 8b 05 00 00 00 00 mov 0x0(%rip),%rax # 0x15
15: 48 8b 05 00 00 00 00 mov 0x0(%rip),%rax # 0x1c
}}}
One would expect each of the 4 mov instructions to get fixed up, instead there are 4 fixups for the first instruction.
I think the fix would be to make the tobytes bytecode callback take an extra parameter that is either buf/mybuf or the current offset into the buffer.
|
yasm_output_value_func gets the wrong offseet
|
https://api.github.com/repos/yasm/yasm/issues/13/comments
| 0 |
2011-06-24T16:50:23Z
|
2011-06-24T16:50:23Z
|
https://github.com/yasm/yasm/issues/13
| 1,111,230 | 13 |
[
"yasm",
"yasm"
] |
The listing for conditional jumps do not match the output. For short backward jumps it is 2 bytes too short. For short forward is 2 bytes too long. For near jumps backward is 8 bytes short. For near jumps forward it is 8 bytes long.
|
x86_64 mode and x86 mode - listing - conditional jumps not the same as the output. Output correct.
|
https://api.github.com/repos/yasm/yasm/issues/12/comments
| 1 |
2011-06-24T16:50:20Z
|
2023-05-31T02:04:31Z
|
https://github.com/yasm/yasm/issues/12
| 1,111,228 | 12 |
[
"yasm",
"yasm"
] |
yasm complains about the USE32 specification that is used in nasm-style sourcecode quite often:
segment .code USE32
segment .data USE32
It´s just a warning, but I am wondering whether there is a good reason for that warning, or whether it can be turned off.
|
OBJ32 warnings
|
https://api.github.com/repos/yasm/yasm/issues/11/comments
| 0 |
2011-06-24T16:50:17Z
|
2011-06-24T16:50:17Z
|
https://github.com/yasm/yasm/issues/11
| 1,111,227 | 11 |
[
"yasm",
"yasm"
] |
The following error happens when using a newer Cython. The attached patch fixes it.
## Error compiling Cython file:
...
# Link to associated data mechanism to keep Python references paired with
# yasm objects.
#
cdef class **assoc_data_callback:
cdef yasm_assoc_data_callback *cb
def __new**(self, destroy, print_):
## ^
yasm.pyx:100:4: **new** method of extension type will change semantics in a future version of Pyrex and Cython. Use **cinit** instead.
|
Fix build for Cython-0.14.1
|
https://api.github.com/repos/yasm/yasm/issues/10/comments
| 0 |
2011-06-24T16:34:32Z
|
2011-06-24T16:34:33Z
|
https://github.com/yasm/yasm/issues/10
| 1,111,146 | 10 |
[
"yasm",
"yasm"
] |
When using a pop instruction without a suffix in 64-bit mode, for example:
pop -24(%rcx)
YASM incorrectly generated a popw instruction instead of a popq.
See below comparing yasm to gas:
$ cat pop.s
pop -24(%rcx)
$ ./yasm -f macho64 -p gas -o pop.o pop.s
$ otool -t -v pop.o
pop.o:
(__TEXT,__text) section
0000000000000000 popw 0xe8(%rcx)
$ as -o pop.o pop.s
$ otool -t -v pop.o
pop.o:
(__TEXT,__text) section
0000000000000000 popq 0xe8(%rcx)
|
64bit pop incorrectly generated as popw
|
https://api.github.com/repos/yasm/yasm/issues/9/comments
| 0 |
2011-06-24T16:34:30Z
|
2011-06-24T16:34:30Z
|
https://github.com/yasm/yasm/issues/9
| 1,111,145 | 9 |
[
"yasm",
"yasm"
] |
Hello again,
I'm a bit confused with the pre-processor concatination. I am not saying it is wrong, tbh I am not sure how I would like it to work.
There may be some syntax I'm not aware of that solves this?
Imagine the following example:
{{{
%macro concat_label 1
_label_%1:
%endmacro
%macro concat_jump 1
jmp _label_%1
%endmacro
%macro concat_jumps 2
%assign i %1
%rep %2
concat_jump i
%assign i (i + 1)
%endrep
%endmacro
concat_label 0x01 ; Will create _label_0x01
concat_jumps 0x01, 1 ; Creates a jump table to the one label.
; However, due to the %assign(?), the hex-notation
; is lost and _label_1 is referenced -> error
}}}
I think that "concat_label 0x01" should create the label _label_0x01. I also think that concat_jumps is behaving correctly. However, there is an obvious conflict here :(
Maybe add support to do something like (this is where I belive that I might be missing some syntax ;)),
{{{
%macro concat_label 1
%assign i %1 ; Lose the hex-notation
_label_%%i: ; Create _label_1 (C-style concatination)
%endmacro
}}}
Is this an issue or are there already walk-arounds?
Regards and thanks for an absolutly awesome assembler :D
//Pellsson
|
Macro concatination
|
https://api.github.com/repos/yasm/yasm/issues/8/comments
| 0 |
2011-06-24T16:34:27Z
|
2011-06-24T16:34:27Z
|
https://github.com/yasm/yasm/issues/8
| 1,111,144 | 8 |
[
"yasm",
"yasm"
] |
When in startup-default mode for win64, i.e. ABSOLUTE, the following code,
(in code section:)
mov rax, [symb]
....
(in data section:)
symb dq 12345678h
is assembled without problems, but the Visual Studio linker complains about a ADDR32 fixup.
Work-around: set YASM do DEFAULT rel mode.
1) Why does this work? (relative mode is relative to rip, which is the code pointer, not a data pointer)
2) Wouldn't it be better is YASM emitted correct code also in its default, i.e., abs mode?
In a similar vein, if I have to pass the address of one function to another by storing it, like
mov [_si], func
first YASM complains about non-matching sizes. Though YASM does not tell the truth here (anyway, how can it know?),
this one is easy to fix:
mov qword [_si], func
Now YASM likes what it sees, but again Visual Studio does not and complains again about ADDR32 fixup. For this problem,
I did not find any work-around.
|
32-bit fixup in Win64 .obj
|
https://api.github.com/repos/yasm/yasm/issues/7/comments
| 0 |
2011-06-24T16:31:51Z
|
2011-06-24T16:31:51Z
|
https://github.com/yasm/yasm/issues/7
| 1,111,132 | 7 |
[
"yasm",
"yasm"
] |
I believe there is a problem with the use of dd when using 64 bit registers, namely rax... essentially one memory expression runs into the other, which means that when one expression is altered so to is the other.
the compiler fails to warn about this behaviour.
I use
standard
yasm -f elf -g dwarf2 -m amd64 FILENAME.asm
ld -o FILENAME FILENAME.o
the simplest fix to the problem is to use dq expressions instead of dd
or to place a dummy dd expression between them, however
I believe the compiler should warn about this eventuallity
I have included the simple program I have built to show this problem
|
dd words memory expressions, overriding each other with 64 bit registers
|
https://api.github.com/repos/yasm/yasm/issues/6/comments
| 0 |
2011-06-24T16:31:48Z
|
2011-06-24T16:31:48Z
|
https://github.com/yasm/yasm/issues/6
| 1,111,131 | 6 |
[
"yasm",
"yasm"
] |
"vpshift_insn" structure based instructions should not allows 2 operand forms. VPSXX
|
vpshift instructions do not have 2 operand form
|
https://api.github.com/repos/yasm/yasm/issues/5/comments
| 0 |
2011-06-24T16:31:46Z
|
2011-06-24T16:31:46Z
|
https://github.com/yasm/yasm/issues/5
| 1,111,130 | 5 |
[
"yasm",
"yasm"
] |
After retrying the latest Yasm, we didn't found it supported COMDAT section for Windows like what generated by __declspec(selectany) by Visual Studio. Please support this feature because it is a solution for some C++ features.
|
Support COMDAT section/symbol for Windows(COFF)
|
https://api.github.com/repos/yasm/yasm/issues/4/comments
| 0 |
2011-06-24T16:31:43Z
|
2011-06-24T16:31:43Z
|
https://github.com/yasm/yasm/issues/4
| 1,111,129 | 4 |
[
"yasm",
"yasm"
] |
our project (mpc-hc) needs to make GCC generated code compatible with MSVC /SAFESEH linker option (everything must be in one binary file - that's concept), so we tried to compile in 2 steps - to ASM by GCC and to objects by YASM[[BR]]
enlisting problems in order from more important to less important:[[BR]]
1) missing .secrel32 command results in broken object[[BR]]
2) missing .set command (this one should be easy to fix) - brocken objects[[BR]]
3) missing .loc command - probably brocken objects too[[BR]]
4) missing .def command - affects only debug info according to docs[[BR]]
5) missing movzd command - can be fixed (presumably) by replacing to movzx[[BR]]
6) missing /nop (with operand) , /APP and /NO_APP - but they seem to have no impact when stripped from files
|
missing GAS commands/unable to build GCC-generated ASM files
|
https://api.github.com/repos/yasm/yasm/issues/3/comments
| 0 |
2011-06-24T16:31:40Z
|
2011-06-24T16:31:40Z
|
https://github.com/yasm/yasm/issues/3
| 1,111,128 | 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.