Thread overview | |||||||
---|---|---|---|---|---|---|---|
|
November 08, 2018 [Issue 19375] .init of a nested struct stumps the inliner | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19375 Basile B. <b2.temp@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |b2.temp@gmx.com See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=16360 --- Comment #1 from Basile B. <b2.temp@gmx.com> --- just a nested type is sufficiet to prevent inlining. possibly a duplicated of https://issues.dlang.org/show_bug.cgi?id=16360 -- |
November 08, 2018 [Issue 19375] .init of a nested struct stumps the inliner | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19375 --- Comment #2 from Stanislav Blinov <stanislav.blinov@gmail.com> --- They seem to be different. In your case, it's about defining a struct inside the inlined function (note that that struct isn't event nested, i.e. __traits(isNested, S) will be false. In my case, it's about using a nested struct inside another function. Although who knows, it may indeed boil down to the same problem in DMD's code. -- |
March 21, 2020 [Issue 19375] .init of a nested struct stumps the inliner | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19375 Basile-z <b2.temp@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|b2.temp@gmx.com | -- |
December 17, 2022 [Issue 19375] .init of a nested struct stumps the inliner | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19375 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P3 -- |
December 27, 2022 [Issue 19375] .init of a nested struct stumps the inliner | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19375 mhh <maxhaton@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |maxhaton@gmail.com Resolution|--- |WORKSFORME --- Comment #3 from mhh <maxhaton@gmail.com> --- Cannot reproduce with the new inliner. -- |
Copyright © 1999-2021 by the D Language Foundation