[Bug libfortran/31099] [4.3/4.2 regression] Runtime error on legal code using RECL

2007-03-09 Thread Thomas dot Koenig at online dot de
--- Comment #5 from Thomas dot Koenig at online dot de 2007-03-09 20:13 --- Subject: Re: [4.3/4.2 regression] Runtime error on legal code using RECL I believe I have a fix. I am testing now. We were not initializing a few things when we have a record length given. Index: io

[Bug fortran/30981] a ** exp fails for integer exponents if exp is -huge()-1 (endless loop)

2007-02-28 Thread Thomas dot Koenig at online dot de
--- Comment #11 from Thomas dot Koenig at online dot de 2007-02-28 23:13 --- Subject: Re: a ** exp fails for integer exponents if exp is -huge()-1 (endless loop) --- Comment #10 from pinskia at gcc dot gnu dot org 2007-02-28 22:39 --- Yes declare this as undefined code

[Bug fortran/30452] Strange syntax error with high-value character

2007-01-13 Thread Thomas dot Koenig at online dot de
--- Comment #3 from Thomas dot Koenig at online dot de 2007-01-13 08:42 --- Subject: Re: Strange syntax error with high-value character jvdelisle at gcc dot gnu dot org wrote: Turns out that the character 254 which is Hex FE is also the 2's complement representation of -2 which

[Bug fortran/30452] Strange syntax error with high-value character

2007-01-13 Thread Thomas dot Koenig at online dot de
--- Comment #4 from Thomas dot Koenig at online dot de 2007-01-13 11:51 --- Subject: Re: Strange syntax error with high-value character jvdelisle at gcc dot gnu dot org wrote: Turns out that the character 254 which is Hex FE is also the 2's complement representation of -2 which

[Bug fortran/19292] [meta-bug] g77 features lacking in gfortran

2006-05-27 Thread Thomas dot Koenig at online dot de
--- Comment #21 from Thomas dot Koenig at online dot de 2006-05-27 20:24 --- Subject: Re: [meta-bug] g77 features lacking in gfortran sgk at troutmask dot apl dot washington dot edu wrote: 27757 does not belong in this meta-bug. It is actually a regression with respect

[Bug fortran/13082] Function entries and entries with alternate returns not implemented

2005-04-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-08 07:36 --- Subject: Re: Function entries and entries with alternate returns not implemented You wrote (in bugzilla): - We tried out the designed successor and found it very immature. In fact it is not even

[Bug bootstrap/20783] New: [4.1 Regression] Bootstrapping 4.1 takes 50% longer than 4.0

2005-04-06 Thread Thomas dot Koenig at online dot de
dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20783

[Bug bootstrap/20783] [4.1 Regression] Bootstrapping 4.1 takes 50% longer than 4.0

2005-04-06 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-06 14:21 --- This goes away when --disable-checking is specified for 4.0 and 4.1. Closing as invalid. -- What|Removed |Added

[Bug libfortran/20744] size= isn't implemented correctly

2005-04-05 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-05 07:17 --- This is fixed with http://gcc.gnu.org/bugzilla/attachment.cgi?id=8525action=view (an attachment to PR 20661). Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20744

[Bug libfortran/20744] New: size= isn't implemented correctly

2005-04-04 Thread Thomas dot Koenig at online dot de
Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu

[Bug libfortran/20744] size= isn't implemented correctly

2005-04-04 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added Keywords||wrong-code Known to fail||4.0.0 4.1.0

[Bug fortran/18481] [g77 regression] ICE with assigned integer variable format

2005-04-01 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-01 11:45 --- No write or print statement is necessary: $ cat assign.f90 program main assign 1000 to i 1000 format (A) end $ gfortran assign.f90 $ gfortran -fdump-parse-tree assign.f90 In file

[Bug libfortran/20661] End of record not detected

2005-04-01 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-04-01 13:34 --- This patch fixes the test case. It also includes my EOR patch for advancing I/O. This is regression-tested on mainline. I'll submit a proper patch when I have finished regression-testing it on 4.0

[Bug libfortran/20661] End of record not detected

2005-03-29 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-29 15:11 --- I'll try and have a look. Hopefully, my copyright papers that I sent off on 2005-03-19 will come through sometime soon, because the end-of-record patch at http://gcc.gnu.org/ml/gcc-patches/2005-03

[Bug fortran/20618] New: Variable format expressions not supported

2005-03-24 Thread Thomas dot Koenig at online dot de
ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20618

[Bug fortran/20618] Variable format expressions not supported

2005-03-24 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-24 14:29 --- Actually, implementing this would be a bit harder than I thought. It seems that the variable expression is evaluated at runtime, so you can do things like $ cat v-fmt2.f program main

[Bug fortran/20592] New: -fno-automatic (g77 option) is missing from gfortran.

2005-03-22 Thread Thomas dot Koenig at online dot de
Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http

[Bug fortran/20592] -fno-automatic (g77 option) is missing from gfortran.

2005-03-22 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added OtherBugsDependingO||19292 nThis|| Severity|normal

[Bug fortran/20538] compiling -finline-functions -O2 and we crash at runtime

2005-03-19 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-19 13:20 --- (In reply to comment #8) Due to general gfortran lameness only contained functions are ever inlined. Top-level functions are never inlined. Why? I've worked with a Fortrtran 77 compiler (vor

[Bug middle-end/20545] New: unnecessary operations in tailcall

2005-03-18 Thread Thomas dot Koenig at online dot de
operations in tailcall Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de

[Bug middle-end/20517] New: bit shift/mask optimization potential

2005-03-17 Thread Thomas dot Koenig at online dot de
Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20517

[Bug middle-end/20517] bit shift/mask optimization potential

2005-03-17 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added Keywords||missed-optimization http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20517

[Bug middle-end/20432] complex reciprocal has too many operations

2005-03-17 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-17 13:41 --- (In reply to comment #3) I cannot remember the rules but -0.0 * 0.0 could be -0.0 (and not 0.0), someone needs to help me here. I'm trying to see what input could apply to, but I can't think of one

[Bug libfortran/20471] Segmentation fault on read after backspace and rewind

2005-03-17 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-17 14:40 --- (In reply to comment #2) The patches suggested in comment #2 under bug 20156 fixes bugs 20156, 20125 and 20471 on the macintosh and does not seem to cause any new problems. Can you submit

[Bug libfortran/19014] print *,maxloc(array) segfaults

2005-03-15 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added BugsThisDependsOn||19106 AssignedTo|unassigned at gcc dot gnu |Thomas dot Koenig at online |dot org

[Bug libfortran/20092] console input doesn't deal correctly with CR

2005-03-13 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-13 21:10 --- I believe this is also fixed with http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00729.html Copyright papers, where are you? :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20092

[Bug libfortran/19106] segfault in executable for print *,sum(a,dim=2,mask=a0)

2005-03-13 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-13 22:11 --- Patch here: http://gcc.gnu.org/ml/fortran/2005-03/msg00232.html -- What|Removed |Added

[Bug bootstrap/20437] New: bootstrap --enable-maintainer-mode broken

2005-03-12 Thread Thomas dot Koenig at online dot de
Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20437

[Bug libfortran/20438] New: conflicting types for int8_t with --enable-maintainer-mode

2005-03-12 Thread Thomas dot Koenig at online dot de
dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20438

[Bug middle-end/20434] pessimization of complex expression

2005-03-12 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-12 09:45 --- (In reply to comment #4) (In reply to comment #3) - Why the casts to double? Because that is required by the C standard. Isn't that covered by the as-if rule? I'm fairly sure the cast

[Bug libfortran/19106] segfault in executable for print *,sum(a,dim=2,mask=a0)

2005-03-12 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-12 22:52 --- The 0 as data pointer is a signal to the library that it needs to fill out the properties of the array, because the front end can't determine it. See http://gcc.gnu.org/ml/fortran/2005-03/msg00199

[Bug middle-end/20434] pessimization of complex expression

2005-03-12 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-12 23:13 --- (In reply to comment #6) Well the real reason is creal/cimag returns double and not float. Use crealf/cimagf instead. You're right, of course. Doing that gets me bb 0: foo (cr, ci); return cr

[Bug middle-end/20432] New: complex reciprocal has too many operations

2005-03-11 Thread Thomas dot Koenig at online dot de
Priority: P2 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20432

[Bug libfortran/19155] blanks not treated as zeros in 'E' format read (NIST FM110.FOR)

2005-03-11 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-11 21:21 --- My vote would go for fixing this, because of the NIST testsuite failure. Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19155

[Bug middle-end/20432] complex reciprocal has too many operations

2005-03-11 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-11 21:36 --- (In reply to comment #1) D.2395 * 0.0 Can trap if D.2395 is a non quiet NAN. D.2395 gets its value from D.2395 = SR.23 / SR.24; two lines earlier. Is there anything that would generate

[Bug middle-end/20434] pessimization of complex expression

2005-03-11 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-11 21:59 --- There are two strange things here: - Why the + 0. ? - Why the casts to double? -- What|Removed |Added

[Bug middle-end/20434] New: pessimization of complex expression

2005-03-11 Thread Thomas dot Koenig at online dot de
Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20434

[Bug middle-end/20434] pessimization of complex expression

2005-03-11 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-11 22:49 --- - Why the casts to double? Because that is required by the C standard. Isn't that covered by the as-if rule? I'm fairly sure the cast to double won't change the result of the operator

[Bug libfortran/18958] eoshift segfaults when shifting off the end of an array

2005-03-09 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-09 15:13 --- $ cat eoshift.f90 print *,eoshift((/1, 3/), 3) end $ gfortran eoshift.f90 $ ./a.out Segmentation fault This fails because the loop for (n = 0; n len; n++) { memcpy (dest

[Bug fortran/20323] optional arguments incorrectly accepted in specification expressions

2005-03-09 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-09 16:01 --- The complaint is a segfault at runtime when you actually want to do anything with the string whose length depends on a missing optional argument. This isn't too bad (the same thing happens if you

[Bug libfortran/18495] Intrinisc function SPREAD is broken

2005-03-09 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-09 23:33 --- This looks very much like a front end bug. The along parameter gets the wrong value. Look at this: $ cat test_spread.f90 program test_spread implicit none integer, parameter :: N = 1000

[Bug libfortran/20131] gfortan - incorrectly reads beyond the end of line.

2005-03-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-08 08:20 --- Updated patch: http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00729.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20131

[Bug libfortran/19568] incorrect formatted read

2005-03-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-08 08:21 --- Updated patch: http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00729.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19568

[Bug fortran/15080] Forall bounds not calculated correctly (forall_3.f90)

2005-03-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-08 15:35 --- Here's a somewhat reduced testcase that fails for me on ia64-unknown-linux-gnu: $ cat forall_5.f90 program evil_forall implicit none type t logical valid integer :: s integer, dimension

[Bug fortran/20387] New: ICE in gfc_conv_array_initializer

2005-03-08 Thread Thomas dot Koenig at online dot de
in gfc_conv_array_initializer Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs

[Bug fortran/15080] Forall bounds not calculated correctly (forall_3.f90)

2005-03-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-08 20:30 --- On i686-pc-linux-gnu, forall_5.f90 does the following: $ gfortran forall_5.f90 $ ./a.out Fortran runtime error: Attempt to allocate a negative amount of memory. $ gfortran -v Using built-in specs

[Bug libfortran/19568] incorrect formatted read

2005-03-06 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-06 23:34 --- Updated patch: http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00566.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19568

[Bug libfortran/20131] gfortan - incorrectly reads beyond the end of line.

2005-03-06 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-06 23:34 --- Patch: http://gcc.gnu.org/ml/gcc-patches/2005-03/msg00566.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20131

[Bug libfortran/16339] Unformatted i/o on large arrays inefficient

2005-03-04 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-04 10:47 --- This is really _very_ inefficient, by a factor of 20. Some test numbers: $ g77 write-record.f $ time ./a.out real0m1.819s user0m1.774s sys 0m0.044s $ gfortran write-record.f $ time

[Bug libfortran/20278] Performance regression in formatted output vs. g77

2005-03-03 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-03 20:27 --- Same thing on i686: $ gfortran write-many.f $ time ./a.out real0m5.576s user0m5.508s sys 0m0.038s $ g77 write-many.f $ time ./a.out real0m3.252s user0m3.185s sys 0m0.041s

[Bug libfortran/20278] New: Performance regression in formatted output vs. g77

2005-03-02 Thread Thomas dot Koenig at online dot de
ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: ia64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20278

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-03-01 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-01 15:43 --- (In reply to comment #14) (In reply to comment #13) (In reply to comment #11) I get the same as I got above with the following version on x86: GNU C version 4.0.0 20050225 (experimental) (i686-pc

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-03-01 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-01 21:07 --- Andrew, I'm sorry if I'm not making myself clear here. The problem that I see is that, on ia64-unknown-linux-gnu and on i386-pc-linux-gnu, with clean trees, I see code like L2:; D.2390 = 0.0 / SR

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-03-01 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-03-01 21:26 --- (In reply to comment #18) L2:; D.2390 = 0.0 / SR.22; D.2392 = SR.22 + D.2390 * 0.0; c$real = (D.2371 + D.2372 * D.2390) / D.2392; c$imag = (D.2372 - D.2371 * D.2390) / D.2392

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-02-28 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-28 20:55 --- Comment #7 shows that there is still something to be done for (br+I*bi)/a (with real br, bi, a). This could be simplified to br/a + I*bi/a, which isn't happening. Thomas -- What

[Bug middle-end/18902] Naive (default) complex division algorithm

2005-02-28 Thread Thomas dot Koenig at online dot de
-- Bug 18902 depends on bug 19953, which changed state. Bug 19953 Summary: Special-case real + complex arithmetic operation (-ffast-math) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19953 What|Old Value |New Value

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-02-28 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-28 20:55 --- What I meant was comment#8 *sigh* -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19953

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-02-27 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-27 12:52 --- Is this really fixed? Look at this: $ cat c-div.c #include math.h #include complex.h int main() { float a; complex float b,c; foo(a,b); c = b/a; return creal(c) + cimag(c) 0

[Bug libfortran/20163] gfortran - error opening direct access file

2005-02-26 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-26 20:46 --- Patch for the first bug here: http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01694.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20163

[Bug libfortran/20163] gfortran - error opening direct access file

2005-02-26 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-26 20:49 --- Here is a reduced test case for the second error: $ cat open-after-error.f open(10,status=foo,err=100) call abort 100 continue open(10,status=scratch) end $ cat open-after

[Bug libfortran/20131] gfortan - incorrectly reads beyond the end of line.

2005-02-23 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-23 12:28 --- I'll check later wether this is fixed with the proposed fix for PR 19568 to be found at http://gcc.gnu.org/ml/gcc-patches/2005-01/msg02295.html Thomas -- What|Removed

[Bug libfortran/20131] gfortan - incorrectly reads beyond the end of line.

2005-02-23 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-23 21:27 --- No, this isn't fixed with the patch I referred to earlier. Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20131

[Bug libfortran/20179] cannot mix C and Fortran I/O

2005-02-23 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-23 22:54 --- Add fflush(stdout); at the end of cio.c, and things work as expected. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20179

[Bug libfortran/20163] gfortran - error opening direct access file

2005-02-23 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-23 23:09 --- This is two bugs. The first bug can be reduced to $ cat open-opt.f open(unit=10,status=scratch ) end $ gfortran open-opt.f $ ./a.out At line 1 of file open-opt.f Fortran runtime error: Bad

[Bug libfortran/20163] gfortran - error opening direct access file

2005-02-23 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-23 23:29 --- This has a pretty good chance of fixing it. Proper testing, Changelog entry, ... tomorrow. Index: string.c === RCS file: /cvsroot/gcc

[Bug libfortran/20092] gfortran not correctly padding keyboard or text file input

2005-02-20 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added CC||Thomas dot Koenig at online ||dot de http://gcc.gnu.org

[Bug libfortran/20074] New: reshape of pointer array segfaults at runtime

2005-02-19 Thread Thomas dot Koenig at online dot de
of pointer array segfaults at runtime Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot

[Bug libfortran/20037] libfortran: format termination bug in formatted write

2005-02-18 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-18 10:42 --- I think this is identical to PR 15332. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20037

[Bug target/19974] incorrect complex division on ia-64 with flag_complex_method = 2

2005-02-17 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-17 09:42 --- (In reply to comment #7) Using Mathematica I get for (10^20 + 10^12 I)/(1 - 10^-8) = 10^20 + 2 * 10^12 I so really neither of them are mathematically correct. The test case was (10^20-10^12*I)/(1

[Bug target/19974] incorrect complex division on ia-64 with flag_complex_method = 2

2005-02-17 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-17 13:52 --- Another datapoint - the fact that slarrb has problems has been confirmed by a Lapack developer. A new version is slated to appear as a patch soon. Hopefully, this will reduce the potential hang

[Bug middle-end/19974] incorrect complex division on ia-64 with flag_complex_method = 2

2005-02-16 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-16 12:41 --- I think I have identified the problem. The hang itself is probably caused by a Lapack bug, because slarrb is only fed 0. and NaN as arguments. The reason why this is so is probably due to a problem

[Bug middle-end/19974] incorrect complex division on ia-64 with flag_complex_method = 2

2005-02-16 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-16 20:51 --- Checking this on i686-unknown-linux-gnu, I find the same result with flag_complex_method=2 as on ia-64. I am also seeing the same result with logarithmic scaling (using frexp and ldexp). Maybe I'm

[Bug middle-end/19953] Special-case real + complex arithmetic operation (-ffast-math)

2005-02-15 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-15 10:29 --- And in fact this only can happen with -funsafe-math-optimizations (or maybe with -fno-trapping- math because a+0.0 can trap. Hmm... if b is complex and has the value (0., signalling NaN

[Bug middle-end/19974] New: Lapack hang in xeigtstc on ia-64

2005-02-15 Thread Thomas dot Koenig at online dot de
Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: ia64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19974

[Bug middle-end/19974] Lapack hang in xeigtstc on ia-64

2005-02-15 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added OtherBugsDependingO||5900 nThis|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19974

[Bug middle-end/19974] Lapack hang in xeigtstc on ia-64

2005-02-15 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added Keywords||wrong-code http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19974

[Bug middle-end/19974] Lapack hang in xeigtstc on ia-64

2005-02-15 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-15 20:14 --- This does not happen on an Athlon-xp with -march=athlon-xp -mfmath=sse. Might be target or 64-bit specific. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19974

[Bug target/18977] [4.0 regression] LAPACK test xeigtsts segfaults with optimization

2005-02-14 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-14 12:25 --- I can confirm that this is fixed in the 20050213 snapshot. Both the reduced C test case and the original Fortran routine don't segfault any more. Thanks to whoever fixed this :-) I would suggest

[Bug middle-end/19953] New: Special-case real*complex multiplication for flag_complex_method=2

2005-02-14 Thread Thomas dot Koenig at online dot de
for flag_complex_method=2 Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC

[Bug middle-end/19953] Special-case real*complex multiplication for flag_complex_method=2

2005-02-14 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added OtherBugsDependingO||18902 nThis|| Keywords|

[Bug middle-end/19953] Special-case real + complex arithmetic operation

2005-02-14 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-14 20:06 --- Same thing for complex division, where the performance penalty is probably also pretty severe: $ cat c-div.c #include math.h #include complex.h int main() { float a; complex float b,c

[Bug middle-end/19953] [4.0 regression] Special-case real + complex arithmetic operation

2005-02-14 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-14 22:38 --- For addition, this is a regression against 3.3.5: $ cat c-add.c #include math.h #include complex.h int main() { float a; complex float b,c; foo(a,b); c = b+a; return creal(c

[Bug fortran/19936] New: confused error message about implied do loop

2005-02-13 Thread Thomas dot Koenig at online dot de
Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla

[Bug fortran/19928] Reference of constant derived type component causes failure

2005-02-13 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-13 17:50 --- Looking at PR 17123 a bit more closely, I think that this is a duplicate. Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19928

[Bug driver/19848] options passed from -verbose-asm do not adequately reflect optimization

2005-02-10 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-10 08:52 --- (In reply to comment #2) There are a gazillion places where we just check if (optimize) without any specific flag. It would be quite a lot of work to introduce flags for all of them, and I'm not sure

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-10 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-10 10:17 --- It appears the problem is caused by one of the optimization options that cannot be controlled with flags. One suspect is this code snippet from gcc/config/ia64.c : static bool ia64_rtx_costs (rtx x

[Bug driver/19825] -fno-loop-optimize2 does not work

2005-02-10 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-10 20:31 --- *** This bug has been marked as a duplicate of 19848 *** -- What|Removed |Added

[Bug driver/19848] options passed from -verbose-asm do not adequately reflect optimization

2005-02-10 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-10 20:31 --- *** Bug 19825 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19848

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-10 Thread Thomas dot Koenig at online dot de
-- Bug 5900 depends on bug 19825, which changed state. Bug 19825 Summary: -fno-loop-optimize2 does not work http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19825 What|Old Value |New Value

[Bug driver/19848] options passed from -verbose-asm do not adequately reflect optimization

2005-02-10 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-10 20:35 --- (In reply to comment #4) $ find . -name '*.c' | xargs grep '[(|!] *optimize[) =!|]' | wc -l 204 Any idea how I should go about further debugging PR 5900? There is a wrong-code for ia-64

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-09 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-09 08:12 --- gfortran -c -O1 -fno-tree-ccp -fno-tree-ch -fno-tree-copyrename -fno-tree-dce -fno-tree-dominator-opts -fverbose-asm -fno-unswitch-loops -fno-peel-loops -fno-unroll-loops -fno-tree-dse -fno-tree-fre

[Bug driver/19848] New: options passed from -verbose-asm do not adequately reflect optimization

2005-02-09 Thread Thomas dot Koenig at online dot de
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19848

[Bug driver/19848] options passed from -verbose-asm do not adequately reflect optimization

2005-02-09 Thread Thomas dot Koenig at online dot de
-- What|Removed |Added OtherBugsDependingO||5900 nThis|| Version|unknown |4.0.0

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-09 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-09 12:43 --- See PR 19848. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5900

[Bug driver/19848] options passed from -verbose-asm do not adequately reflect optimization

2005-02-09 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-09 21:19 --- Same thing on i686-pc-linux-gnu with the gcc driver: $ cat main.c int main() { return 0; } $ gcc -S -fverbose-asm -o main-o0.s main.c $ gcc -S -fno-cprop-registers -fno-defer-pop -fno-guess

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-08 09:24 --- On ia64-unknown-linux-gnu, -O1 produces the same result that -O3 does. Here's a shell script that I currently use for shotgun testing of single optimization options: for a in \ branch-count-reg cprop

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-08 15:36 --- (In reply to comment #34) Please, try the opposite: disable optimizations through -O1 -fno-[optnam] and see if you find out something. Still the same four failures with #! /bin/sh

[Bug driver/19825] New: -fno-loop-optimize2 does not work

2005-02-08 Thread Thomas dot Koenig at online dot de
: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org

[Bug driver/19825] -fno-loop-optimize2 does not work

2005-02-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-08 16:36 --- This blocks testing of compiler options in PR 5900. -- What|Removed |Added

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-08 Thread Thomas dot Koenig at online dot de
--- Additional Comments From Thomas dot Koenig at online dot de 2005-02-08 16:36 --- I am not sure which of my tests of compiler options were actually testing anything. There appears to be a bug in passing at least one -fno - switch (see PR 19825). Thomas -- http://gcc.gnu.org

  1   2   3   4   >