Re: error: matching constraint references invalid operand number

2022-03-05 Thread rempas via D.gnu
On Saturday, 5 March 2022 at 17:31:17 UTC, Iain Buclaw wrote: With the option "--help=d" Alright! This will do the trick! Thanks a lot for your time and thanks a lot for your amazing work in GDC in general!

Re: error: matching constraint references invalid operand number

2022-03-05 Thread Iain Buclaw via D.gnu
On Saturday, 5 March 2022 at 10:04:43 UTC, rempas wrote: Thank you! This will do the trick! Do you happen to know if D plans to add "registers" in the future or if it has been suggested but was rejected? core.attribute (or more specifically, gcc.attributes, which is where all the documented

Re: error: matching constraint references invalid operand number

2022-03-05 Thread rempas via D.gnu
On Friday, 4 March 2022 at 23:33:12 UTC, Iain Buclaw wrote: GCC doesn't have constraints for registers %r8 .. %15. As D doesn't have register variables either, you'll have to set-up r10 in the instruction string. ``` asm { "mov %[rem], %%r10; syscall" : "=a" (ret_code) : "a" (230), "D"

Re: error: matching constraint references invalid operand number

2022-03-04 Thread Iain Buclaw via D.gnu
On Friday, 4 March 2022 at 17:18:56 UTC, rempas wrote: When I try to compile, I'm getting the following error message: ``` source/time.d: In function ‘sys_clock_nanosleep’: source/time.d:132:31: error: matching constraint references invalid operand number 132 | : "memory&quo

error: matching constraint references invalid operand number

2022-03-04 Thread rempas via D.gnu
"=a" (ret_code) : "a" (230), "D" (clock), "S" (flags), "d" (req), "r10" (rem) : "memory", "rcx", "r11"; } return ret_code; } ``` When I try to compile, I'm getting the following error message