[Bug fortran/31197] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31197

[Bug fortran/31198] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31198

[Bug fortran/31199] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31199

[Bug fortran/31200] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31200

[Bug fortran/31201] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31201

[Bug fortran/31202] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31202

[Bug fortran/31203] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31203

[Bug fortran/31204] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31204

[Bug fortran/31205] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31205

[Bug fortran/31206] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31206

[Bug fortran/31207] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31207

[Bug fortran/31208] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31208

[Bug fortran/31209] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31209

[Bug fortran/31210] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31210

[Bug fortran/31211] New: wrong code generated with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
-- Summary: wrong code generated with gfortran Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk

[Bug fortran/31212] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla

[Bug fortran/31213] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31213

[Bug fortran/31214] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31214

[Bug fortran/31215] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31215

[Bug fortran/31216] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31216

[Bug fortran/31217] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31217

[Bug fortran/31218] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31218

[Bug fortran/31219] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31219

[Bug fortran/31220] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31220

[Bug fortran/31221] New: ICE on valid code with gfortran

2007-03-16 Thread jv244 at cam dot ac dot uk
with gfortran Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-16 Thread jv244 at cam dot ac dot uk
--- Comment #85 from jv244 at cam dot ac dot uk 2007-03-16 11:52 --- (In reply to comment #84) Could you post your cpuflags? There should be lahf_lm flag present for opterons. flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-16 Thread jv244 at cam dot ac dot uk
--- Comment #86 from jv244 at cam dot ac dot uk 2007-03-16 12:07 --- (In reply to comment #85) (In reply to comment #84) Could you post your cpuflags? There should be lahf_lm flag present for opterons. sorry, the previous post was of the wrong machine... these are the correct

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-16 Thread jv244 at cam dot ac dot uk
--- Comment #89 from jv244 at cam dot ac dot uk 2007-03-16 14:16 --- Thanks for your reports! and you for your fixes... things are back to working now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975

[Bug tree-optimization/30965] Fails to tree-combine conditions in COND_EXPRs

2007-03-16 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2007-03-16 19:38 --- just to keep track, patch here: http://gcc.gnu.org/ml/gcc-patches/2007-03/msg00129.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30965

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-14 Thread jv244 at cam dot ac dot uk
--- Comment #77 from jv244 at cam dot ac dot uk 2007-03-14 14:48 --- Currently GNU Fortran (GCC) 4.3.0 20070313 (experimental) there seems to be a new gcc error on CP2K: gfortran -c -O3 -ftree-loop-linear -ftree-vectorize -ffast-math -march=opteron -msse2 fparser.f90 /tmp

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-14 Thread jv244 at cam dot ac dot uk
--- Comment #79 from jv244 at cam dot ac dot uk 2007-03-14 15:14 --- (In reply to comment #78) Could you post the temporary asm (only lines around line 820 will be enough) to check what is going wrong? .L157: movslq %r13d,%rax imulq %rsi, %rax addq

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-14 Thread jv244 at cam dot ac dot uk
--- Comment #82 from jv244 at cam dot ac dot uk 2007-03-14 16:29 --- Huh, I somehow misread opteron for athlon. Your code is OK for x86_64, but it looks to me that you will have to upgrade binutils. upgrading binutils is not much of an option for me, but with -march=x86-64 I get

[Bug middle-end/30835] ICE with -O2 -ftree-loop-linear

2007-03-14 Thread jv244 at cam dot ac dot uk
--- Comment #3 from jv244 at cam dot ac dot uk 2007-03-14 16:30 --- (In reply to comment #2) this issue now seems fixed on trunk for me as well, so I guess this could be closed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30835

[Bug tree-optimization/31079] New: 300% difference between ifort/gfortran

2007-03-08 Thread jv244 at cam dot ac dot uk
% difference between ifort/gfortran Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk

[Bug tree-optimization/31079] 300% difference between ifort/gfortran

2007-03-08 Thread jv244 at cam dot ac dot uk
--- Comment #1 from jv244 at cam dot ac dot uk 2007-03-08 11:11 --- The following is (for me) an even more interesting example, as it times only the loop that thus the actual multiply / add but also tricks my version of ifort into generating the expected asm. Ifort is about twice

[Bug tree-optimization/31040] New: unroll/peel loops not aggressive enough

2007-03-05 Thread jv244 at cam dot ac dot uk
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla

[Bug tree-optimization/31040] unroll/peel loops not aggressive enough

2007-03-05 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2007-03-05 11:47 --- (In reply to comment #1) We don't unroll non-innermost loops at the moment. I don't know if sccp can be taught to handle this case (and if it's worth it). such small loops are quite typical for some quantum

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-03 Thread jv244 at cam dot ac dot uk
--- Comment #75 from jv244 at cam dot ac dot uk 2007-03-03 10:12 --- Joost. I wonder if you have done OpenMP testing, also (I imagine that, OpenMP being frequently broken on cp2k and gfortran being a free compiler OpenMP-capable, you might have tried it :) No, haven't tried it yet

[Bug rtl-optimization/31021] New: gfortran 20% slower than ifort on CP2K computational kernel

2007-03-02 Thread jv244 at cam dot ac dot uk
Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31021

[Bug rtl-optimization/31021] gfortran 20% slower than ifort on CP2K computational kernel

2007-03-02 Thread jv244 at cam dot ac dot uk
--- Comment #1 from jv244 at cam dot ac dot uk 2007-03-02 08:39 --- Created an attachment (id=13131) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13131action=view) gfortran kernel asm -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31021

[Bug rtl-optimization/31021] gfortran 20% slower than ifort on CP2K computational kernel

2007-03-02 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2007-03-02 08:39 --- Created an attachment (id=13132) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13132action=view) ifort kernel asm -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31021

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-03-02 Thread jv244 at cam dot ac dot uk
--- Comment #73 from jv244 at cam dot ac dot uk 2007-03-02 08:41 --- I've added PR 31021 to track some performance issue with gfortran on one of CP2K's kernels. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975

[Bug rtl-optimization/31021] gfortran 20% slower than ifort on CP2K computational kernel

2007-03-02 Thread jv244 at cam dot ac dot uk
--- Comment #4 from jv244 at cam dot ac dot uk 2007-03-02 09:55 --- (In reply to comment #3) On my AMD Athlon(tm) 64 X2 Dual Core Processor 4800+, gfortran is in x86_64 mode only 13% slower: gfortran: Kernel time 5.872366, real 0m33.121s; user 0m32.898s; sys 0m0.088s. Ifort

[Bug rtl-optimization/31021] gfortran 20% slower than ifort on CP2K computational kernel

2007-03-02 Thread jv244 at cam dot ac dot uk
--- Comment #5 from jv244 at cam dot ac dot uk 2007-03-02 18:15 --- grid_fast.F:483: note: not vectorized: can't determine dependence between (*coef_447)[D.1967_2320] and (*coef_447)[D.1967_2320] DO icoef=1,coef_max coef(icoef,1)=coef(icoef,1

[Bug tree-optimization/31029] New: missed otimization

2007-03-02 Thread jv244 at cam dot ac dot uk
org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31029

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-19 Thread jv244 at cam dot ac dot uk
--- Comment #72 from jv244 at cam dot ac dot uk 2007-02-19 19:51 --- I checked that gfortran yields correct results for the CP2K testsuite with the options: -O0 -g -fbounds-check and -O3 -ffast-math -funroll-loops -ftree-vectorize -fomit-frame-pointer -msse2 -march=native I've added

[Bug fortran/30869] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30869

[Bug fortran/30870] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30870

[Bug fortran/30871] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
: incorrect error message for valid code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http

[Bug fortran/30872] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30872

[Bug fortran/30873] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30873

[Bug fortran/30874] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30874

[Bug fortran/30875] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
message for valid code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http

[Bug fortran/30876] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
-- Summary: incorrect error message for valid code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac

[Bug fortran/30877] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30877

[Bug fortran/30878] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
message for valid code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http

[Bug fortran/30879] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug fortran/30880] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30880

[Bug fortran/30881] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30881

[Bug fortran/30882] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30882

[Bug fortran/30883] New: incorrect error message for valid code

2007-02-19 Thread jv244 at cam dot ac dot uk
for valid code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-17 Thread jv244 at cam dot ac dot uk
--- Comment #69 from jv244 at cam dot ac dot uk 2007-02-17 09:17 --- (In reply to comment #68) Current gfortran compiles the code with the standard -OX switches, however, still ICEs with '-O2 -fbounds-check -ftree-vectorize -ftree-loop-linear -ffast-math -O2 -msse3' on our local

[Bug middle-end/30835] New: ICE with -O2 -ftree-loop-linear

2007-02-17 Thread jv244 at cam dot ac dot uk
: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30835

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-17 Thread jv244 at cam dot ac dot uk
--- Comment #71 from jv244 at cam dot ac dot uk 2007-02-17 16:17 --- (In reply to comment #68) Current gfortran compiles the code with the standard -OX switches, however, still ICEs with '-O2 -fbounds-check -ftree-vectorize -ftree-loop-linear -ffast-math -O2 -msse3' on our local

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-16 Thread jv244 at cam dot ac dot uk
--- Comment #68 from jv244 at cam dot ac dot uk 2007-02-17 07:50 --- Current gfortran compiles the code with the standard -OX switches, however, still ICEs with '-O2 -fbounds-check -ftree-vectorize -ftree-loop-linear -ffast-math -O2 -msse3' on our local opteron. all_cp2k_gfortran.f90

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-15 Thread jv244 at cam dot ac dot uk
--- Comment #65 from jv244 at cam dot ac dot uk 2007-02-16 05:57 --- (In reply to comment #64) I now have a machine at home here running i686-pc-gnu-linux that I plan to set up daily compile test on. Joost, does that link in coment #63 get updated daily? No, the idea is that you

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-13 Thread jv244 at cam dot ac dot uk
--- Comment #60 from jv244 at cam dot ac dot uk 2007-02-13 09:20 --- When you have a moment, could you confirm that all is now well with trunk, please? Once again, I am sorry about the breakage. Now I see Daniel's testcase, I realise that I could easily have devised a test

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-13 Thread jv244 at cam dot ac dot uk
--- Comment #63 from jv244 at cam dot ac dot uk 2007-02-13 20:04 --- Well, I'd add it to my testsuite if weren't a PITA to figure out how to make it build. wget http://www.pci.unizh.ch/vandevondele/tmp/all_cp2k_gfortran.f90.gz gunzip all_cp2k_gfortran.f90.gz gfortran -c

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #48 from jv244 at cam dot ac dot uk 2007-02-12 15:56 --- Currently, there is a new ICE on CP2K (see initial comment) that happens at any optimisation level: gfortran -c all_cp2k_gfortran.f90 all_cp2k_gfortran.f90:118549: internal compiler error: Segmentation fault Please

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #50 from jv244 at cam dot ac dot uk 2007-02-12 17:09 --- I really think CP2K should be added to some nightly tester somewhere by gfortran developers... Well, I second that, but we first need to get it working (like, the middle-end people have to move on PR30391

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #51 from jv244 at cam dot ac dot uk 2007-02-12 17:12 --- I'm pretty sure it's the same problem that was already reported here: http://gcc.gnu.org/ml/fortran/2007-02/msg00250.html Of course, a confirmation wouldn't hurt, but I don't have time right now. If you manage

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #53 from jv244 at cam dot ac dot uk 2007-02-12 17:52 --- (In reply to comment #52) I don't know if this triggers something, looks like a simple statement. Yes that triggers my memory of PR 30391. No, that one only happens at -O1 and above, the current ICE is at -O0

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #55 from jv244 at cam dot ac dot uk 2007-02-12 18:26 --- Nonetheless, I do not see it being associated with my doo-doo in module.c, do you? I'm not an expert, but this is a traceback, leading to module.c: Program received signal SIGSEGV, Segmentation fault

[Bug fortran/30779] New: incomplete file triggers ICE

2007-02-12 Thread jv244 at cam dot ac dot uk
: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30779

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #57 from jv244 at cam dot ac dot uk 2007-02-12 19:18 --- Yes, that's the one: http://gcc.gnu.org/ml/fortran/2007-02/msg00250.html for people reducing the bug, I found that it is in the module cp_fm_pool_types. This indicates the the line number indicated in the segfault

[Bug fortran/30779] incomplete file triggers ICE

2007-02-12 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2007-02-12 20:12 --- (In reply to comment #1) Confirmed. Backtrace: (gdb) r t.f90 Starting program: /home/ig25/libexec/gcc/i686-pc-linux-gnu/4.3.0/f951 t.f90 Failed to read a valid object file image from memory. t.f90:1: cat

[Bug libfortran/15516] assembly snippets for nano second resolution wall clock time

2007-02-11 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2007-02-11 10:55 --- (In reply to comment #0) If you extract the object file get_clockfreq.o from /usr/lib/librt.a then you can call the function __get_clockfreq() to determine clock frequency. To extract the routine, try: ar xv

[Bug middle-end/30391] [4.3 regression] ICE at -O1 with conditional expressions and GIMPLE_MODIFY_STMT

2007-02-05 Thread jv244 at cam dot ac dot uk
--- Comment #6 from jv244 at cam dot ac dot uk 2007-02-05 20:12 --- a patch: http://gcc.gnu.org/ml/gcc-patches/2007-02/msg00353.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30391

[Bug target/30484] Miscompilation of remainder expressions on CPUs of the i386 family

2007-01-16 Thread jv244 at cam dot ac dot uk
--- Comment #5 from jv244 at cam dot ac dot uk 2007-01-17 07:14 --- (In reply to comment #0) The program below shows (at all the optimization levels) a miscompilation of the remainder expression that causes INT_MIN % -1 to cause a SIGFPE on CPUs of the i386 family. notice

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-01-05 Thread jv244 at cam dot ac dot uk
--- Comment #44 from jv244 at cam dot ac dot uk 2007-01-06 06:30 --- Current gcc ICEs again on CP2K: gfortran -c -O3 -ftree-vectorize -ffast-math -march=opteron -fopenmp mc_coordinates.f90 mc_coordinates.f90: In function ‘check_for_overlap’: mc_coordinates.f90:192: internal compiler

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-19 Thread jv244 at cam dot ac dot uk
--- Comment #40 from jv244 at cam dot ac dot uk 2006-12-19 12:49 --- I've now checked that gcc trunk (revision 120045) compiles CP2K (at -O3 -ftree-vectorize -ffast-math -march=opteron) and that the numerical results seem acceptable. Great job... I hope the the original file is kept

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-13 Thread jv244 at cam dot ac dot uk
--- Comment #37 from jv244 at cam dot ac dot uk 2006-12-13 14:01 --- (In reply to comment #36) well, this was reduced, filed as PR30147, and fixed. Tobias reduced another one and filed it as PR30190 (see dependencies). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975

[Bug fortran/30200] New: valgrind errors for write statement

2006-12-13 Thread jv244 at cam dot ac dot uk
: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30200

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-13 Thread jv244 at cam dot ac dot uk
--- Comment #39 from jv244 at cam dot ac dot uk 2006-12-13 15:25 --- I had a look at one of the failing testcases from CP2K testsuite, and under valgrind there were a number of errors that could be reproduced in the small testcase of PR30200 -- http://gcc.gnu.org/bugzilla

[Bug fortran/30200] valgrind errors for write statement

2006-12-13 Thread jv244 at cam dot ac dot uk
--- Comment #1 from jv244 at cam dot ac dot uk 2006-12-13 19:28 --- This problem seems to be at the root of most CP2K regtest failures described in PR29975 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30200

[Bug libfortran/30200] write(*,myfmt=(1X,a,'xyz')) A prints Az' instead of Axyz

2006-12-13 Thread jv244 at cam dot ac dot uk
--- Comment #7 from jv244 at cam dot ac dot uk 2006-12-14 06:41 --- (In reply to comment #6) More information. I get Tobias bad result with -m64 on x86-64-Linux. The problem goes away with -m32. $ gfortran -m32 pr30200-2.f90 $ ./a.out Axyz $ gfortran -m64 pr30200-2.f90

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-11 Thread jv244 at cam dot ac dot uk
--- Comment #30 from jv244 at cam dot ac dot uk 2006-12-11 09:51 --- (In reply to comment #29) simple testcase for the segfault: SUBROUTINE S(unit_number) character(len=100) :: status_string integer :: unit_number,istat status_string=KEEP CLOSE (UNIT=unit_number,IOSTAT=istat,STATUS

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-11 Thread jv244 at cam dot ac dot uk
--- Comment #32 from jv244 at cam dot ac dot uk 2006-12-11 11:29 --- (In reply to comment #31) gcc version 4.3.0 20061210 (experimental) simple testcase for the segfault: I tried it with gfortran 4.3 and 4.2 (today's build) and an older 4.1 build and neither crashes. valgrind

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-11 Thread jv244 at cam dot ac dot uk
--- Comment #33 from jv244 at cam dot ac dot uk 2006-12-11 11:54 --- Running the CP2K regtests now results in: number of FAILED tests 24 (these are just the runs that do not complete, I have not checked that the runs that finish also generate the right numbers. This can be reproduced

[Bug fortran/29975] [meta-bugs] [4.1 and 4.2 only] ICEs with CP2K

2006-12-11 Thread jv244 at cam dot ac dot uk
--- Comment #35 from jv244 at cam dot ac dot uk 2006-12-11 16:08 --- (In reply to comment #34) CP2k actually gives here an ICE with -O2 (PR 30147) at least when I use ./do_regtest (otherwise I didn't saw it). I did not yet look at why the calculation results are wrong. yes, I'm

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-12-02 Thread jv244 at cam dot ac dot uk
--- Comment #12 from jv244 at cam dot ac dot uk 2006-12-02 13:37 --- I am not sure that I see how the test case in #6 can ever have worked; if it is indeed representative of the code in CP2K, I do not see how that can have worked either. fparser is a relatively new addition

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-12-02 Thread jv244 at cam dot ac dot uk
--- Comment #13 from jv244 at cam dot ac dot uk 2006-12-02 13:55 --- (In reply to comment #11) Created an attachment (id=12724) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12724action=view) [edit] test case for interface bl_copy all_cp2k_gfortran.f90:418697.22: USE

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-12-02 Thread jv244 at cam dot ac dot uk
--- Comment #14 from jv244 at cam dot ac dot uk 2006-12-02 14:00 --- Are you in a position to try the patch on CP2K? no quite so easy right now, but I'll be svn updating as soon as it is in. Looks like tobias anyway tested it OK. your PRs have given me something absorbing

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-11-29 Thread jv244 at cam dot ac dot uk
--- Comment #8 from jv244 at cam dot ac dot uk 2006-11-29 22:26 --- (In reply to comment #7) Joost, Do you happen to know at what revision things went bad? I'm afraid I don't... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-11-28 Thread jv244 at cam dot ac dot uk
--- Comment #5 from jv244 at cam dot ac dot uk 2006-11-28 15:36 --- after the fix for 29976 I get with current mainline : all_cp2k_gfortran.f90:347635: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http

[Bug fortran/25620] Missed optimization with power

2006-11-27 Thread jv244 at cam dot ac dot uk
--- Comment #16 from jv244 at cam dot ac dot uk 2006-11-27 16:49 --- (In reply to comment #15) Fixed (partly) on the mainline. We can now expand pow (x, n/2) and pow (x, n/3) properly using sqrt and/or cbrt, but cbrt is not available from the fortran frontend (it misses to define

[Bug fortran/29975] New: [metabug] ICEs with CP2K

2006-11-25 Thread jv244 at cam dot ac dot uk
at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975

[Bug fortran/29975] [meta] ICEs with CP2K

2006-11-25 Thread jv244 at cam dot ac dot uk
--- Comment #2 from jv244 at cam dot ac dot uk 2006-11-25 14:15 --- (In reply to comment #1) Hi Joost, I'll look into it. I now regularly build cp2k with gfortran (usually 4.2 branch) on i686-linux for my work but I haven't see this ICE yet. Just in case, what's the platform

[Bug fortran/25620] Missed optimization with power

2006-09-04 Thread jv244 at cam dot ac dot uk
--- Comment #9 from jv244 at cam dot ac dot uk 2006-09-04 14:10 --- (In reply to comment #7) Looking at how we deal with all this, we seem to like pow() very much during folding, even doing the reverse transformations you suggest. The transformation back to sqrt ( x**N ) with N

[Bug web/12821] dead link on onlinedocs/gccint/Top-Level.html

2006-06-12 Thread jv244 at cam dot ac dot uk
--- Comment #3 from jv244 at cam dot ac dot uk 2006-06-12 07:18 --- (In reply to comment #0) still failing ... since it has been opened about 2.5y ago, should it be closed as wontfix ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12821

<    5   6   7   8   9   10   11   12   >