[Issue 17197] Link failure with -m64 on Windows

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17197

Rainer Schuetze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Rainer Schuetze  ---
"Invalid UTF-8" exceptions should no longer happen as I changed the critical
path to use byte[] arrays instead of char[] arrays.
Released in https://github.com/dlang/visuald/releases/tag/v0.45.0-beta1

--

[Issue 17197] Link failure with -m64 on Windows

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17197

--- Comment #2 from Rainer Schuetze  ---
-msmode now passed for links with the MS Linker by
https://github.com/dlang/visuald/releases/tag/v0.44-rc2

--

[Issue 17197] Link failure with -m64 on Windows

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17197

Rainer Schuetze  changed:

   What|Removed |Added

 CC||r.sagita...@gmx.de

--- Comment #1 from Rainer Schuetze  ---
You are right that -msmode should be added, but it probably isn't going to make
a lot of difference since the actual encoding is often hard to guess. In my
tests the names displayed in linker messages are never correct for non-ASCII
characters (there are no exceptions, though). Could you provide an example that
raises the exception?

To avoid the exception from occuring, pipedmd should probably never assume
correct UTF-8.

--