From: Mohan E. <gnu...@th...> - 2003-09-28 09:04:07
|
Danny, Would you be able to comment on my post to the gcj java mailing list?: http://gcc.gnu.org/ml/java/2003-09/msg00336.html This is from a MinGW 3.4 CVS build without any MinGW-local patches. I've been able to work around this by building with -mno-stack-arg-probe, but I doubt this is the right thing to do. In particular, jar.exe suddenly stopped working, though I don't know if this is related. (Haven't had time to investigate.) Since there are no MinGW-local patches for the 3.4 tree, yet, I don't know if this _alloca issue has been fixed with the 3.3 local patches. And unfortunately, I can't use a 3.3 (Linux,MinGW) cross to build a 3.4 native MinGW compiler. So I guess what I'm asking is: - Do you know if the fix for this _alloca bug supposed to be fixed in GCC CVS, the MinGW-local patches, or not at all? - If the answer is "in the MinGW-local patches", then isn't the stability of any of my interim builds (i.e. 3.4) that don't incorporate any MinGW-local patches seriously compromised? - Do you want me to follow up on this in any way? Thanks. -- Mohan http://www.thisiscool.com/ http://www.animalsong.org/ |