[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread jv244 at cam dot ac dot uk
--- Comment #19 from jv244 at cam dot ac dot uk 2007-06-20 08:48 --- (In reply to comment #17) Here is the fix which I am testing, basically instead of creating (typeof(array[0] *)array we create array[lb]: did this fix test OK ? Since it fixes the CP2K issue, I would hope that it

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread fxcoudert at gcc dot gnu dot org
--- Comment #20 from fxcoudert at gcc dot gnu dot org 2007-06-20 08:52 --- (In reply to comment #19) did this fix test OK ? Since it fixes the CP2K issue, I would hope that it could be posted for review soon. The patch is OK to commit along with a testcase from this PR. --

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread pinskia at gmail dot com
--- Comment #21 from pinskia at gmail dot com 2007-06-20 13:22 --- Subject: Re: [4.3 Regression] Miscompilation with -O1 did this fix test OK ? Since it fixes the CP2K issue, I would hope that it could be posted for review soon. I can't get to testing this patch fully until Friday

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread rguenth at gcc dot gnu dot org
--- Comment #22 from rguenth at gcc dot gnu dot org 2007-06-20 13:53 --- It would be nice if a fortraner could make the testcase not output to stdout/err but to /dev/null instead. open(6,'/dev/null') didn't work for me ;) Just to make a testcase suitable for the testsuite. --

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread rguenth at gcc dot gnu dot org
--- Comment #23 from rguenth at gcc dot gnu dot org 2007-06-20 13:55 --- stupid me. open(6,file='/dev/null') works. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32140

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread jv244 at cam dot ac dot uk
--- Comment #24 from jv244 at cam dot ac dot uk 2007-06-20 14:03 --- (In reply to comment #22) It would be nice if a fortraner could make the testcase not output to stdout/err but to /dev/null instead. open(6,'/dev/null') didn't work for me ;) Just to make a testcase

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread pinskia at gcc dot gnu dot org
--- Comment #25 from pinskia at gcc dot gnu dot org 2007-06-20 14:03 --- Here is a testcase which also checks the resulting array is correct: MODULE TEST CONTAINS PURE FUNCTION s2a_3(s1,s2,s3) RESULT(a) CHARACTER(LEN=*), INTENT(IN) :: s1, s2, s3 CHARACTER(LEN=1000),

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread pinskia at gcc dot gnu dot org
--- Comment #26 from pinskia at gcc dot gnu dot org 2007-06-20 14:05 --- (In reply to comment #25) Here is a testcase which also checks the resulting array is correct: oh s/eq/ne/ I did not test mine and it is 11pm and I have to get up early in the morning. --

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread rguenther at suse dot de
--- Comment #27 from rguenther at suse dot de 2007-06-20 14:07 --- Subject: Re: [4.3 Regression] Miscompilation with -O1 On Wed, 20 Jun 2007, jv244 at cam dot ac dot uk wrote: --- Comment #24 from jv244 at cam dot ac dot uk 2007-06-20 14:03 --- (In reply to comment

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread rguenth at gcc dot gnu dot org
--- Comment #28 from rguenth at gcc dot gnu dot org 2007-06-20 14:57 --- Subject: Bug 32140 Author: rguenth Date: Wed Jun 20 14:57:10 2007 New Revision: 125886 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=125886 Log: 2007-06-20 Andrew Pinski [EMAIL PROTECTED] Richard

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-20 Thread rguenth at gcc dot gnu dot org
--- Comment #29 from rguenth at gcc dot gnu dot org 2007-06-20 14:59 --- Fixe.d -- rguenth at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-17 Thread pault at gcc dot gnu dot org
--- Comment #14 from pault at gcc dot gnu dot org 2007-06-17 17:54 --- A slight modification of the example in comment #2: MODULE TEST CONTAINS FUNCTION s2a_3(s1) RESULT(a) CHARACTER(LEN=*), INTENT(IN) :: s1 CHARACTER(LEN=LEN(s1)) :: a(3) a(1)=s1 END FUNCTION

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-17 Thread pinskia at gcc dot gnu dot org
--- Comment #16 from pinskia at gcc dot gnu dot org 2007-06-17 21:45 --- I was wrong in marking this as a middle-end issue. We have: char[0:D.1026][1:4] * __result.0; char * temp.87; ... temp.87 = (*__result.0)[0]; __builtin_memset (temp.87 + (unnamed-unsigned:32) _s1, 32, 4 -

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-17 Thread pinskia at gcc dot gnu dot org
--- Comment #17 from pinskia at gcc dot gnu dot org 2007-06-17 22:08 --- Here is the fix which I am testing, basically instead of creating (typeof(array[0] *)array we create array[lb]: Index: trans.c === --- trans.c

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2007-06-18 01:49 --- Patch tested OK on x86-64-Gnu-Linux. I am also able to compile and run cp2k where before I was getting a segfault. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32140

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-16 Thread jv244 at cam dot ac dot uk
--- Comment #13 from jv244 at cam dot ac dot uk 2007-06-16 19:04 --- (In reply to comment #12) note this might get cleared up with pointer_plus. I have not tried it there yet but i will be posting a patch and committing soon. I've tried current trunk (which should contain

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-15 Thread jv244 at cam dot ac dot uk
--- Comment #10 from jv244 at cam dot ac dot uk 2007-06-15 14:43 --- The segfault is still happening with today's code. This is the simplest case I find to trigger it. MODULE TEST CONTAINS FUNCTION s2a_3(s1) RESULT(a) CHARACTER(LEN=*), INTENT(IN) :: s1

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-15 Thread fxcoudert at gcc dot gnu dot org
--- Comment #11 from fxcoudert at gcc dot gnu dot org 2007-06-15 15:12 --- (In reply to comment #10) but I can't see how I could debug further pretty please, can somebody look into that... I'd like to be able to test all the stuff that went in since the bug was opened a few

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-15 Thread pinskia at gmail dot com
--- Comment #12 from pinskia at gmail dot com 2007-06-15 15:22 --- Subject: Re: [4.3 Regression] Miscompilation with -O1 On 15 Jun 2007 15:12:02 -, fxcoudert at gcc dot gnu dot org [EMAIL PROTECTED] wrote: When (and if) I get some time after my PhD defence (next monday), I'll try

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-12 Thread fxcoudert at gcc dot gnu dot org
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-06-12 15:47 --- I see it also with today's compiler on i686-darwin: $ gfortran test.f90 -O2 ./a.out a.bb ccc -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-06-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2007-06-13 00:55 --- Also see failure at optimizations -O1, -O2, -O3 on x86-64-gnu-linuz (intel) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32140

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-05-29 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-05-29 15:32 --- Regression happens between 2007-05-25-r125057 and 2007-05-29-r125159. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32140] [4.3 Regression] Miscompilation with -O1

2007-05-29 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2007-05-29 15:41 --- I assume this is another incarnation of this bugs but leads to a segfault and a slightly different valgrind output: MODULE TEST CONTAINS PURE FUNCTION s2a_3(s1,s2,s3) RESULT(a) CHARACTER(LEN=*), INTENT(IN)