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... | 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 a... | 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, READONL... | 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 di... | 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... | 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 ... | 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 upda... | 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/y... | 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/kitche... | 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 genera... | 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 i... | %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/pro... | 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)...... | 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
Se... | 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-o... | 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... | 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 ... | 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 ... | 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
... | 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
GL... | 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 wi... | 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](h... | 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... | 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 `resu... | 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 51af4082cc898b122b88f11fd34033fc00fad... | 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... | 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 anythin... | 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
... | 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,... | 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... | 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... | %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... | 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 ve... | 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 mult... | 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 ... | 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.s... | 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, yo... | 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 ... | 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
}}}
jus... | 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 mat... | 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 rel... | 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 thi... | 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... | 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 impo... | 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... | 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 ass... | 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 ... | 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 $(MAK... | 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,... | 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' ... | 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 n... | 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 pr... | 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 ... | 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 on... | 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, p... | 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
000000000... | 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
jm... | 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... | 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.a... | 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 .... | 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.