Bug 6831 – mangled name over 128 characters becomes unreadable

Status
RESOLVED
Resolution
WONTFIX
Severity
normal
Priority
P2
Component
dmd
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2011-10-19T11:52:00Z
Last change time
2015-06-09T05:10:40Z
Assigned to
nobody
Creator
kekeniro2

Comments

Comment #0 by kekeniro2 — 2011-10-19T11:52:26Z
I found that when a mangled name is very long, it turns into UNREADABLE characters. And the limit of the length is 128 characters.( It is too short! ) ----- Beginning of source module manglingtest; // length of module name is significant! class MyClass { } void tfunc(T, U)(T a, U b) { } void main() { auto a = new MyClass; auto b = new MyClass; tfunc(a,b); // wrong mangling } ----- End of source (Additional) I am using a tool to read build messages and map files, so such unreadables are especially inconvenienced. And I want to write for profiler's output, too. Environment: D2.055 Windows XP SP3 32-bit
Comment #1 by simen.kjaras — 2011-10-19T12:57:08Z
This is a limitation of the current linker. Until a linker comes around that can handle humongous names, this will not be fixed. Walter is in the process of rewriting the linker, so perhaps this will eventually be fixed, but don't hold your breath.
Comment #2 by bugzilla — 2012-01-21T00:23:51Z
It'll have to wait until we move to a new object file format.