--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-09-03
19:09 ---
*** Bug 23264 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23262
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-09-03
10:15 ---
OK, it's worse than I thought. When you open a file with O_BINARY, it is opened
using Unix conventions, and you need to add yourself the \r in the right places.
Otherwise, you can use the Windows CRLF con
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-09-03
08:46 ---
Well, that was not so difficult: when we write "1234\n6789\n" for example, the
length of the write is 10. But the size of the resulting file is 12, since each
newline character is translated into a two-byt
--
What|Removed |Added
GCC host triplet|i386-mingw32|
GCC target triplet|mingw32 |i386-mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=232
--
What|Removed |Added
Summary|rewind truncates file on|[migwin32] rewind truncates
|migwin32|file
http://gcc.gnu.org/bugzilla/