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.
Comment #2 by ibuclaw — 2015-05-22T09:24:53Z
Comment #3 by ibuclaw — 2015-05-22T10:24:50Z
Comment #4 by github-bugzilla — 2015-05-22T13:52:43Z
Comment #5 by k.hara.pg — 2015-05-30T14:33:52Z
PR was merged.
Comment #6 by github-bugzilla — 2015-06-17T21:02:57Z
Comment #7 by github-bugzilla — 2017-07-19T17:41:43Z
Commit pushed to dmd-cxx at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/482d8fc456e7089edb6811ac7e1bc5dbef82296c Issue 14566 - Return function attribute not handled in core.demangle