[Bug c++/35159] g++ and gfortran inoperable with no error message

2009-06-24 Thread ktietz at gcc dot gnu dot org
--- Comment #25 from ktietz at gcc dot gnu dot org 2009-06-24 10:28 --- This bug was fixed for 4.4 version. The real issue here was the changes happend to ira and specifying one register via the constrains =a or +a. Both variant don't work anymore. By expanding the stack_allocator

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-10-20 Thread ktietz at gcc dot gnu dot org
--- Comment #24 from ktietz at gcc dot gnu dot org 2008-10-20 11:24 --- This bug is reasoned by some problems in ira. IIUC, mingw 32-bit has the same issue here. This bug can be worked around by disable ira optimization via -fno-ira. --

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-09-21 Thread pepalogik at seznam dot cz
--- Comment #22 from pepalogik at seznam dot cz 2008-09-21 15:02 --- I'm probably not the one who'll find the core of the bug but I'd like to mention two simple facts: 1: mingw-w64-bin_i686-mingw_20080707 WORKS 2: mingw-w64-bin_x86_64-mingw_20080724 DOESN'T WORK (Vista64 SP1) I don't

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-09-21 Thread nightstrike at gmail dot com
--- Comment #23 from nightstrike at gmail dot com 2008-09-21 17:06 --- (In reply to comment #22) I'm probably not the one who'll find the core of the bug but I'd like to mention two simple facts: Thanks for your feedback! 1: mingw-w64-bin_i686-mingw_20080707 WORKS 2:

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-05-13 Thread nightstrike at gmail dot com
--- Comment #21 from nightstrike at gmail dot com 2008-05-13 13:23 --- ping.. Is there anyone that can help us with this? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-03-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2008-03-08 06:06 --- This looks like bad stuff. See my separate note to see if I can get to a point of reproducing this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-03-06 Thread nightstrike at gmail dot com
--- Comment #19 from nightstrike at gmail dot com 2008-03-06 16:08 --- Ok, compiling the aforementioned Hello, world! program using gfortran --save-temps hello.f90 results in f951.exe maxing out the CPU forever. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-03-05 Thread nightstrike at gmail dot com
--- Comment #16 from nightstrike at gmail dot com 2008-03-06 03:00 --- Created an attachment (id=15267) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15267action=view) Preprocssed source for the testcase mentioned I took the code that I mentioned in the first post in this bug and

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-03-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2008-03-06 04:50 --- What is the Fortran test case that makes this is a gfortran issue? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-03-05 Thread nightstrike at gmail dot com
--- Comment #18 from nightstrike at gmail dot com 2008-03-06 05:09 --- (In reply to comment #17) What is the Fortran test case that makes this is a gfortran issue? PROGRAM HelloWorld WRITE(*,*) Hello World! END PROGRAM I haven't tested that again with the latest changes that

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-02-16 Thread nightstrike at gmail dot com
--- Comment #14 from nightstrike at gmail dot com 2008-02-16 17:22 --- edited title to reflect gfortran failure, as well. -- nightstrike at gmail dot com changed: What|Removed |Added

[Bug c++/35159] g++ and gfortran inoperable with no error message

2008-02-16 Thread ktietz at gcc dot gnu dot org
--- Comment #15 from ktietz at gcc dot gnu dot org 2008-02-16 19:50 --- (In reply to comment #10) (In reply to comment #8) I tested this already and it didn't solved the problem. But may +a is more correct. Perhaps setting RTX_FRAME_RELATED_P is needed? Or gen_blockage() at some