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&action=edit
Initi
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?
++
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).
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?
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
https://gcc.g
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, but
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77277
Jan Niklas Hasse changed:
What|Removed |Added
CC||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 of
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 outpu
10 matches
Mail list logo
