https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88424
--- Comment #5 from Peter Damianov ---
I checked clang's behavior, and it does CRLF -> LF from non-comments, but it
leaves them intact in comments. I'm not really sure if this behavior is worth
emulating or not. I think it would be better to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88424
--- Comment #4 from Peter Damianov ---
All of the non-commments are turned to LF line endings.
So it must be something specifically to do with comment processing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88424
--- Comment #3 from Peter Damianov ---
Looking in a hex editor, what gcc is doing is changing the CRLF to LFLF, there
is no CR in the output.
/* If the file is using old-school Mac line endings (\r only),
terminate with another \r, not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88424
--- Comment #2 from Christoph Reiter ---
For context, we use gcc in gobject-introspection where we parse metadata from
the C comments and this breaks things when users on Windows have git set up to
auto convert line endings:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88424
Andrew Pinski changed:
What|Removed |Added
Component|c |preprocessor
--- Comment #1 from Andrew
