[Bug lto/106700] [13 Regression] O_NONBLOCK does not exist for x86_64-w64-mingw32 host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106700 Martin Liška changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Liška --- Should be fixed now.
[Bug lto/106700] [13 Regression] O_NONBLOCK does not exist for x86_64-w64-mingw32 host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106700 --- Comment #3 from CVS Commits --- The master branch has been updated by Martin Liska : https://gcc.gnu.org/g:827f64135957ce21617cd0345508077439fa29d8 commit r13-2137-g827f64135957ce21617cd0345508077439fa29d8 Author: Martin Liska Date: Thu Aug 18 13:03:42 2022 +0200 jobserver: detect properly O_NONBLOCK PR lto/106700 gcc/ChangeLog: * configure.ac: Detect O_NONBLOCK flag for open. * config.in: Regenerate. * configure: Regenerate. * opts-common.cc (jobserver_info::connect): Set is_connected properly based on O_NONBLOCK. * opts-jobserver.h (struct jobserver_info): Add is_connected member variable. gcc/lto/ChangeLog: * lto.cc (wait_for_child): Ask if we are connected to jobserver. (stream_out_partitions): Likewise.
[Bug lto/106700] [13 Regression] O_NONBLOCK does not exist for x86_64-w64-mingw32 host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106700 Martin Liška changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org --- Comment #2 from Martin Liška --- Mine.
[Bug lto/106700] [13 Regression] O_NONBLOCK does not exist for x86_64-w64-mingw32 host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106700 Andrew Pinski changed: What|Removed |Added URL||https://gcc.gnu.org/piperma ||il/gcc-patches/2022-August/ ||599959.html Status|UNCONFIRMED |NEW Last reconfirmed||2022-08-20 Ever confirmed|0 |1 Keywords||build, patch Target Milestone|--- |13.0 Component|bootstrap |lto Summary|O_NONBLOCK does not exist |[13 Regression] O_NONBLOCK |for x86_64-w64-mingw32 host |does not exist for ||x86_64-w64-mingw32 host --- Comment #1 from Andrew Pinski --- Patch to fix the issue was already submitted two days ago: https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599959.html