Requesting maintainership for Cygwin and mingw-w64 ports
Hello, I'd like to apply for the position of Cygwin and mingw-w64 gcc port maintainer. What do I need to do to accomplish that? signature.asc Description: OpenPGP digital signature
Re: JonY appointed Cygwin and mingw-w64 maintainer
On 6/14/2016 03:07, David Edelsohn wrote: > I am pleased to announce that the GCC Steering Committee has > appointed Jon Y as Cygwin and mingw-w64 maintainer. > > Please join me in congratulating Jon on his new role. > Jon, please update your listing in the MAINTAINERS file. > > Happy hacking! > David > Updated MAINTAINERS file, thanks all! signature.asc Description: OpenPGP digital signature
Re: Test results update for gcc 9.0.0 on x86_64-w64-mingw32
On 09/14/2018 01:50 PM, Rainer Emrich wrote: > https://gcc.gnu.org/ml/gcc-testresults/2018-09/msg01798.html > > Full build and testsuite logs here: > https://cloud.emrich-ebersheim.de/index.php/s/pootRHorSgdtBkG > > If it's of any help I may try to do a bootstrap and testsuite run every > 2 or 3 weeks. > > Rainer > Thanks for setting up and testing gcc! signature.asc Description: OpenPGP digital signature
Re: Heads-Up: early LTO debug to land, breaking Mach-O / [X]COFF
On 05/12/2017 09:24 AM, Richard Biener wrote: > > This is a heads-up that I am in the process of implementing the last > of Jasons review comments on the dwarf2out parts of early LTO debug > support. I hope to post final patches early next week after thoroughly > re-testing everything. > > Note that Mach-O and [X]COFF support in the simple-object machinery > is still missing for the early LTO debug feature so I am going to > break LTOing with DWARF debuginfo on Darwin and Windows (CCing > maintainers). Mach-O support has been worked on a bit by Iain > and myself but the simple-object piece is still missing. > A workaround is to use stabs on these targets with LTO. > > DWARF part: https://gcc.gnu.org/ml/gcc-patches/2016-11/msg01023.html > simple-object part: > https://gcc.gnu.org/ml/gcc-patches/2016-10/msg01733.html > > both still apply with some fuzz. > > Richard. > AFAIK, LTO doesn't work well on Windows to begin with, if non-LTO modes are unaffected, I have no issues with this. signature.asc Description: OpenPGP digital signature
Re: GSoC (Improvements to GCC on Windows)
On 03/14/2018 05:13 PM, Martin Jambor wrote: > Hello, > > On Tue, Mar 13 2018, Ko Phyo wrote: >> Hello >> >> I want to apply the project "Improvements to GCC on Windows" of GCC >> foundation. As a student, I have some theorectical knowledges about C/C++ >> and compiler technologies. And I am sure that the Windows platform has >> steps that are little behind than other open source platforms in pure C/C++ >> technology. So I decided to work on GSoC 2018 with your "Windows >> Improvement program". Please let me know if I am selected as a mentored >> student in yours great project. I will be waiting for your kind reply. > > Well, please note that you still need to apply formally through the GSoC > website to stand a chance to be selected, that does not happen here. > We want students to contact us prior to applying so that their proposals > and goals make sense. > > As far as improving GCC on Windows is concerned, we may find it > challenging to find you a mentor (I am CCing Jonathan Yong, the cygwin > and mingw-w64 maintainer, maybe he has an idea what could be done in > this area as a GSoC project and who might mentor it?). > > Meanwhile, make sure you can build GCC from sources on Windows (I admit > I would not know how to do it myself!) and run the testsuite. > > Good luck, > > Martin > . > Hi, I have been away for work this past month. There is a demand for a proper C++11 threading implementation for Windows using native Windows APIs (post Vista APIs), I have not looked too much into it, nor do I know if the scope is too big or too small for a summer project. Liu Hao has worked on it, and should be familiar with the scope, I have CC'ed him. Never having run any gsoc programs, are there any specific procedures to get it started? signature.asc Description: OpenPGP digital signature
Re: ICE with GCC-4.5.1-20100708
On 7/16/2010 08:46, Yaakov (Cygwin/X) wrote:
On Fri, 2010-07-16 at 02:06 +0200, Angelo Graziosi wrote:
Testing the mingw64-i686* packages found at
ftp://ftp.cygwinports.org/pub/cygwinports/temp/MinGW (Cygwin cross
compiler, see[*]), I have obtained an ICE:
$ cat ICE_test.cpp
void foo(char const* upattern, int color)
{
static short bitmap_data[8];
for (int i = 0; i< 8; i++)
{
bitmap_data[i] = (unsigned char)~upattern[i];
}
}
$ mingw32-g++ -O3 -c ICE_test.cpp
ICE_test.cpp: In function ‘void foo(const char*, int)’:
ICE_test.cpp:1:6: internal compiler error: in vectorizable_store, at
tree-vect-stmts.c:3157
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
Using '-O0/-O1/-O2' in place of '-O3' option, works just fine!
Confirmed. Note that this does not occur with the other cross-targets
compiled from the same snapshot (i686-pc-mingw32, x86_64-w64-mingw32,
i686-pc-linux-gnu), even with -O3.
Yaakov
Cygwin Ports
Adding mingw-w64-public to CC.
Re: GCC 4.8.0 Status Report (2012-10-29), Stage 1 to end soon
On 10/30/2012 01:56, Jakub Jelinek wrote: > Status > == > > I'd like to close the stage 1 phase of GCC 4.8 development > on Monday, November 5th. If you have still patches for new features you'd > like to see in GCC 4.8, please post them for review soon. Patches > posted before the freeze, but reviewed shortly after the freeze, may > still go in, further changes should be just bugfixes and documentation > fixes. > Somebody with commit rights please push "[Patch] Remove _GLIBCXX_HAVE_BROKEN_VSWPRINTF from mingw32-w64/os_defines.h". Kai has already approved, but is off for the week. signature.asc Description: OpenPGP digital signature
