← Back to index | Original Bugzilla link

Bug 17728 – Optlink: Error 168: >64K Global Types

Status
NEW
Severity
normal
Priority
P3
Component
dmd
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2017-08-07T20:14:00Z
Last change time
2024-12-13T18:53:52Z
Keywords
Optlink
Assigned to
No Owner
Creator
Walter Bright
Moved to GitHub: dmd#19297 →

Comments

Comment #0 by bugzilla — 2017-08-07T20:14:00Z
As reported here: https://github.com/DigitalMars/optlink/issues/21 I'm getting this error in a mid-sized application (using vibe-d and another internal library of similar size). It appears that this limit is quite easy to reach with moderate template use. The question is if anything can be done about this in the linker, or if this is a fundamental limitation rooted in the object file format. Message: https://github.com/DigitalMars/optlink/blob/7c096397c052b209cb2cdf2dbe238fecd482239a/common/errors.asm#L1378 Constant: https://github.com/DigitalMars/optlink/blob/7c096397c052b209cb2cdf2dbe238fecd482239a/cv/cvtypcon.asm#L2819
Comment #1 by schveiguy — 2017-08-07T20:41:04Z
Would Rainer's back-reference patch fix the problem?
Comment #2 by r.sagitario — 2017-08-07T21:11:41Z
> Would Rainer's back-reference patch fix the problem? No, this is not about the size of the debug type data in bytes, but the number of entries. That doesn't change with the symbol length. The debug info mostly uses "pretty" names, anyway.
Comment #3 by robert.schadek — 2024-12-13T18:53:52Z
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/19297 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB