[Bug libstdc++/78870] Support std::filesystem on Windows

2017-02-16 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870 --- Comment #8 from Jan Niklas Hasse --- I'm not interested in doing all this work again from scratch, especially since working with the Windows API is a pain.

[Bug libstdc++/78870] New: Support std::filesystem on Windows

2016-12-20 Thread jhasse at bixense dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: jhasse at bixense dot com Target Milestone: --- Currently std::experimental::filesystem / stdc++fs is missing in MSYS2 / MinGW (tested with GCC 6.2.0).

[Bug libstdc++/78870] Support std::filesystem on Windows

2016-12-20 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870 --- Comment #2 from Jan Niklas Hasse --- I'm willing to help. Is there an existing starting point for Windows? Can boost::filesystem's implementation be used?

[Bug libstdc++/78870] Support std::filesystem on Windows

2016-12-21 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870 --- Comment #4 from Jan Niklas Hasse --- > Great! Please read > https://gcc.gnu.org/onlinedocs/libstdc++/manual/appendix_contributing.html > especially the part about legal paperwork. Do you mean the part about legal paperwork in

[Bug libstdc++/78870] Support std::filesystem on Windows

2016-12-21 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870 --- Comment #6 from Jan Niklas Hasse --- > Yes. Okay thanks, I'll look into it. > You can't copy any code, that would be a copyright violation. It's OK to see > which Windows API functions Boost uses for a particular filesystem > operation,

[Bug c++/77277] -fdiagnostics-color=always disabled on _WIN32

2017-03-31 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77277 Jan Niklas Hasse changed: What|Removed |Added CC||jhasse at bixense dot com

[Bug driver/80271] New: Support environment variable CLICOLOR_FORCE to enable -fdiagnostics-color

2017-03-31 Thread jhasse at bixense dot com
: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: jhasse at bixense dot com Target Milestone: --- When piping gcc, colored output gets disabled because isatty returns false. But for many people this is the normal way

[Bug driver/80271] Support environment variable CLICOLOR_FORCE to enable -fdiagnostics-color

2017-09-29 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271 --- Comment #2 from Jan Niklas Hasse --- I guess that's because one doesn't want the build output to depend on an environment variable (most build systems won't rebuild on env variable changes)? -fdiagnostics-color doesn't affect the build

[Bug libfortran/85906] New: Conditional jump depends on uninitialized value in write_decimal / write_integer

2018-05-24 Thread jhasse at bixense dot com
Severity: normal Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: jhasse at bixense dot com Target Milestone: --- Created attachment 44177 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44177=edit Initialize f->

[Bug libfortran/85906] Conditional jump depends on uninitialized value in write_decimal / write_integer

2018-05-28 Thread jhasse at bixense dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85906 --- Comment #8 from Jan Niklas Hasse --- Thanks! If I understand it correctly this will go into 8.1.2?