Bug 14566 – [2.067] core.demangle: New Nj attribute not handled
Status
RESOLVED
Resolution
FIXED
Severity
regression
Priority
P1
Component
druntime
Product
D
Version
D2
Platform
All
OS
All
Creation time
2015-05-10T10:30:00Z
Last change time
2017-07-19T17:41:43Z
Assigned to
nobody
Creator
ibuclaw
Comments
Comment #0 by ibuclaw — 2015-05-10T10:30:25Z
With this code:
---
module demangle
struct test { this(this) { } }
---
In 2.066, the frontend mangling ABI would emit an opAssign as follows:
_D8demangle4test8opAssignMFNcS8demangle4testZS8demangle4test
In 2.067, the frontend now pushes out the following mangled symbol:
_D8demangle4test8opAssignMFNaNbNcNiNjNfS8demangle4testZS8demangle4test
Which, due to the introduction of "Nj" for the STCreturn storage (which is for internal purposes only as far as I can tell), core.demangle is no longer able to demangle it.
Comment #1 by ibuclaw — 2015-05-10T10:50:56Z
Ah, my bad, it's new for the -dip25 switch.
Still, it needs to be handled.