Thread overview
[Bug 291] Compile-time AssemblerTemplate is not supported
May 27, 2018
ARaspiK
May 28, 2018
Iain Buclaw
May 28, 2018
Iain Buclaw
May 27, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=291

--- Comment #1 from ARaspiK <araspik@protonmail.com> ---
I opened the wiki on the Internet Archive. According to the wiki at June 29,
2017, "If the template is not a string literal, use parenthesis to indicate
that it is not an opcode."
This doesn't ACTUALLY WORK. Using `(assemblerTemplate!("syscall"))` doesn't
help whatsoever!

GDC version: `gdc (Gentoo 8.1.0 p1.2) 8.1.0`

-- 
You are receiving this mail because:
You are watching all bug changes.
May 28, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=291

--- Comment #2 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Related to #148.  I wasn't aware of the wiki documentation saying that, maybe we can add support for that effectively closing both.

However at some point I have wanted to redo this so that gdc has exclusive ownership of asm statements - not a could be one syntax or the other depending on the first matched token.

-- 
You are receiving this mail because:
You are watching all bug changes.
May 28, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=291

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |148


Referenced Bugs:

https://bugzilla.gdcproject.org/show_bug.cgi?id=148
[Bug 148] gcc inline asm instruction template must be a constant char string
regression
-- 
You are receiving this mail because:
You are watching all bug changes.
September 01, 2018
https://bugzilla.gdcproject.org/show_bug.cgi?id=291
Bug 291 depends on bug 148, which changed state.

Bug 148 Summary: gcc inline asm instruction template must be a constant char string regression https://bugzilla.gdcproject.org/show_bug.cgi?id=148

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.