[Bug middle-end/31723] Use reciprocal and reciprocal square root with -ffast-math

2007-04-27 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-04-27 11:27 --- (In reply to comment #2) > Note that SSE can vectorize only the float precision variant, not the double > precision one. So one needs to carefuly either disable vectorization for the > double variant to get r

[Bug middle-end/31723] Use reciprocal and reciprocal square root with -ffast-math

2007-04-27 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2007-04-27 11:29 --- (In reply to comment #3) > 1. Convert to single precision > 2. Calculate rcp(s|p)s or rsqrt(p|s)s > 3. Refine with newton iteration > > vs. just using div(p|s)d or sqrt(p|s)d? This should be 1. Co

[Bug middle-end/31723] Use reciprocal and reciprocal square root with -ffast-math

2007-04-27 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2007-04-27 12:01 --- With the benchmarks at http://www.hlnum.org/english/doc/frsqrt/frsqrt.html I get ~/src/benchmark/rsqrt% g++ -O3 -funroll-loops -ffast-math -funit-at-a-time -march=k8 -mfpmath=sse frsqrt.cc ~/src/benchmark/rsqrt

[Bug target/32748] [4.3 regression]: gfortran.dg/array_constructor_6.f90

2007-07-14 Thread jb at gcc dot gnu dot org
--- Comment #8 from jb at gcc dot gnu dot org 2007-07-15 06:57 --- Assigning this bug to myself, since it seems I caused it. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/32748] [4.3 regression]: gfortran.dg/array_constructor_6.f90

2007-07-15 Thread jb at gcc dot gnu dot org
--- Comment #9 from jb at gcc dot gnu dot org 2007-07-15 21:33 --- Subject: Bug 32748 Author: jb Date: Sun Jul 15 21:33:32 2007 New Revision: 126662 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126662 Log: 2007-07-16 Janne Blomqvist <[EMAIL PROTECTED]>

[Bug target/32748] [4.3 regression]: gfortran.dg/array_constructor_6.f90

2007-07-15 Thread jb at gcc dot gnu dot org
--- Comment #10 from jb at gcc dot gnu dot org 2007-07-15 21:35 --- With the 126662 commit, this should now be fixed, closing. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32817] inline (pure) accessor functions

2007-07-24 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-07-24 16:03 --- Confirmed. Gfortran should IMHO not do any inlining itself, rather somehow tell the middle-end when inlining is allowed, and let the middle-end optimizer decide when to actually inline. -- jb at gcc dot gnu dot org

[Bug fortran/32881] New: PURE attribute escapes from contained procedure

2007-07-24 Thread jb at gcc dot gnu dot org
Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32881

[Bug fortran/32879] Document algorithm used for random generator

2007-07-24 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2007-07-24 16:30 --- Confirmed, thought the documentation for RANDOM_NUMBER already mentions that it uses KISS, so this applies only to the legacy intrinsics. -- jb at gcc dot gnu dot org changed: What|Removed

[Bug libfortran/32858] printf-capabilities for runtime_error()

2007-07-24 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2007-07-24 19:06 --- Confirmed. Also, st_sprintf could be directly replaced by s(n)printf. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/32858] printf-capabilities for runtime_error()

2007-07-25 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-07-25 08:46 --- Related to this, a string library for libgfortran: http://gcc.gnu.org/ml/fortran/2007-07/msg00463.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32858

[Bug fortran/32909] New: Replace gfc_c_int_type_node with integer_type_node

2007-07-26 Thread jb at gcc dot gnu dot org
gfc_c_int_type_node with integer_type_node Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: jb at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org

[Bug fortran/32909] Replace gfc_c_int_type_node with integer_type_node

2007-07-27 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2007-07-27 19:53 --- Patch here: http://gcc.gnu.org/ml/gcc-patches/2007-07/msg02008.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32909

[Bug fortran/32909] Replace gfc_c_int_type_node with integer_type_node

2007-07-27 Thread jb at gcc dot gnu dot org
--- Comment #2 from jb at gcc dot gnu dot org 2007-07-27 22:32 --- Subject: Bug 32909 Author: jb Date: Fri Jul 27 22:32:20 2007 New Revision: 127003 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127003 Log: 2007-07-28 Janne Blomqvist <[EMAIL PROTECTED]>

[Bug fortran/32909] Replace gfc_c_int_type_node with integer_type_node

2007-07-27 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-07-27 22:41 --- Fixed, closing. -- jb at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/25297] Support for STRUCTURE/END STRUCTURE and RECORD

2007-07-28 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2007-07-28 20:13 --- Closing as WONTFIX, since nobody seems interested in a) implementing this feature b) maintaining it. As already mentioned, gfortran supports Fortran derived types which can be used for similar purposes as these proposed

[Bug libfortran/32858] printf-capabilities for runtime_error()

2007-07-29 Thread jb at gcc dot gnu dot org
--- Comment #8 from jb at gcc dot gnu dot org 2007-07-29 15:58 --- I had a look at your patch, and one thing which looks worrying is the use of sprintf all over the place. That's just a recipe for buffer overflows, especially when combined with %s formatting. I think Tobi's

[Bug libfortran/25561] Eventually get rid of the Alloc Stream Facility

2007-09-16 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2007-09-16 14:12 --- (In reply to comment #3) > Why marking this as blocking asynchronous I/O? Well, no hard dependency. I just thought it would make sense to do this first, as it would reduce the work required to convert the library t

[Bug fortran/33753] gfortran treads known-to-be-contiguous array as having strides

2007-10-12 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2007-10-12 20:17 --- Gfortran should know that stride==1 for allocatables, as was suggested by Tomas Koenig in #32131, comment 5. *** This bug has been marked as a duplicate of 32131 *** -- jb at gcc dot gnu dot org changed

[Bug fortran/32131] knowing that stride==1 when using allocated arrays and escaping allocatable arrays

2007-10-12 Thread jb at gcc dot gnu dot org
--- Comment #9 from jb at gcc dot gnu dot org 2007-10-12 20:17 --- *** Bug 33753 has been marked as a duplicate of this bug. *** -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/35063] [Regression wrt g77] I/O leaks handles/memory on Windows XP

2008-02-10 Thread jb at gcc dot gnu dot org
--- Comment #35 from jb at gcc dot gnu dot org 2008-02-10 16:55 --- Patch with __gthread_mutex_destroy for all implementations: http://gcc.gnu.org/ml/fortran/2008-02/msg00082.html -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/29549] matmul slow for complex matrices

2008-02-10 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2008-02-10 19:19 --- The big culprit seems to be -fcx-limited-range. The other flags enabled by -ffast-math help very little. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29549

[Bug c/35162] New: Documentation incorrect for -fcx-limited-range

2008-02-11 Thread jb at gcc dot gnu dot org
unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35162

[Bug c/35162] Documentation incorrect for -fcx-limited-range

2008-02-16 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2008-02-16 21:47 --- CC:ing jsm to confirm this bug as people on IRC tell me you're the person that knows about complex in C99. :) -- jb at gcc dot gnu dot org changed: What|Removed |

[Bug fortran/29549] matmul slow for complex matrices

2008-02-16 Thread jb at gcc dot gnu dot org
--- Comment #10 from jb at gcc dot gnu dot org 2008-02-16 22:33 --- Actually, we could compile the entire libgfortran with -fcx-fortran-rules as well: Index: Makefile.am === --- Makefile.am (revision 132367

[Bug middle-end/31738] Fortran dot product vectorization is restricted

2008-02-16 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2008-02-16 22:40 --- Still occurs with 4.3.0 20080216 (experimental) [trunk revision 132367] i.e. only the first procedure (testvectdp) vectorizes, and that only with -ffast-math. -- jb at gcc dot gnu dot org changed

[Bug fortran/29549] matmul slow for complex matrices

2008-02-19 Thread jb at gcc dot gnu dot org
--- Comment #11 from jb at gcc dot gnu dot org 2008-02-19 19:33 --- Patch here: http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00788.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29549

[Bug c/35162] Documentation incorrect for -fcx-limited-range

2008-02-19 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2008-02-19 19:33 --- Patch here: http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00788.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35162

[Bug libfortran/35063] Clean up use of destroy_unit_mutex()

2008-02-23 Thread jb at gcc dot gnu dot org
--- Comment #39 from jb at gcc dot gnu dot org 2008-02-23 18:46 --- (In reply to comment #38) > Janne, do you want to bring your patch from comment #35 up to date and submit > for approval to the lists? Sure, I hope to get it done withing a few days; assigning to myself. --

[Bug fortran/29549] matmul slow for complex matrices

2008-02-25 Thread jb at gcc dot gnu dot org
--- Comment #12 from jb at gcc dot gnu dot org 2008-02-25 19:21 --- Subject: Bug 29549 Author: jb Date: Mon Feb 25 19:20:48 2008 New Revision: 132636 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132636 Log: 2008-02-25 Janne Blomqvist <[EMAIL PROTECTED]>

[Bug c/35162] Documentation incorrect for -fcx-limited-range

2008-02-25 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2008-02-25 19:17 --- Subject: Bug 35162 Author: jb Date: Mon Feb 25 19:16:37 2008 New Revision: 132635 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132635 Log: 2008-02-25 Janne Blomqvist <[EMAIL PROTECTED]>

[Bug fortran/29549] matmul slow for complex matrices

2008-02-25 Thread jb at gcc dot gnu dot org
--- Comment #13 from jb at gcc dot gnu dot org 2008-02-25 19:28 --- Subject: Bug 29549 Author: jb Date: Mon Feb 25 19:27:28 2008 New Revision: 132638 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132638 Log: 2008-02-25 Janne Blomqvist <[EMAIL PROTECTED]>

[Bug c/35162] Documentation incorrect for -fcx-limited-range

2008-02-25 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2008-02-25 19:49 --- Fixed on trunk; closing. -- jb at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug libfortran/35063] Clean up use of destroy_unit_mutex()

2008-02-25 Thread jb at gcc dot gnu dot org
--- Comment #40 from jb at gcc dot gnu dot org 2008-02-25 20:47 --- Updated version of the patch in #35 here: http://gcc.gnu.org/ml/gcc-patches/2008-02/msg01222.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063

[Bug fortran/35385] New: gfortran does not support the COCO preprocessor

2008-02-26 Thread jb at gcc dot gnu dot org
4.4.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35385

[Bug fortran/29549] matmul slow for complex matrices

2008-02-26 Thread jb at gcc dot gnu dot org
--- Comment #14 from jb at gcc dot gnu dot org 2008-02-26 21:15 --- Closing as fixed. Timings for a small test program comparing matrix multiplication done manually vs. libgfortran for real and complex. Results without the committed patch (-O3 -funroll-loops, 1.6 GHz Pentium-M

[Bug libfortran/35063] Clean up use of destroy_unit_mutex()

2008-03-01 Thread jb at gcc dot gnu dot org
--- Comment #41 from jb at gcc dot gnu dot org 2008-03-01 10:52 --- Subject: Bug 35063 Author: jb Date: Sat Mar 1 10:46:31 2008 New Revision: 132800 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132800 Log: gcc: 2008-03-01 Janne Blomqvist <[EMAIL PROTECTED]&g

[Bug libfortran/25561] Eventually get rid of the Alloc Stream Facility

2009-03-22 Thread jb at gcc dot gnu dot org
--- Comment #13 from jb at gcc dot gnu dot org 2009-03-22 10:51 --- Subject: Bug 25561 Author: jb Date: Sun Mar 22 10:51:05 2009 New Revision: 144993 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=144993 Log: 2009-03-22 Janne Blomqvist PR libfortran/25561 li

[Bug fortran/39654] New: ABI bug: FTELL intrinsic function not capable of large files

2009-04-05 Thread jb at gcc dot gnu dot org
P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39654

[Bug libfortran/39665] [4.5 Regression] Fortran IO using unaligned accesses to read/write doubles.

2009-04-08 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2009-04-08 17:11 --- Working on a patch, assigning to myself -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/39670] dollar sign in entities is not recognized when it is first symbol

2009-04-08 Thread jb at gcc dot gnu dot org
--- Comment #16 from jb at gcc dot gnu dot org 2009-04-08 18:24 --- Subject: Bug 39670 Author: jb Date: Wed Apr 8 18:23:55 2009 New Revision: 145767 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145767 Log: 2009-04-08 Janne Blomqvist PR fortr

[Bug libfortran/39665] [4.5 Regression] Fortran IO using unaligned accesses to read/write doubles.

2009-04-08 Thread jb at gcc dot gnu dot org
--- Comment #6 from jb at gcc dot gnu dot org 2009-04-08 20:59 --- (In reply to comment #5) > In addition to the alignment problem, check out the case 10 and case 16 > entries > in the convert_real subroutine. After checking to see that strtold exists, > they actually

[Bug libfortran/39665] [4.5 Regression] Fortran IO using unaligned accesses to read/write doubles.

2009-04-08 Thread jb at gcc dot gnu dot org
--- Comment #8 from jb at gcc dot gnu dot org 2009-04-08 22:36 --- Patch here: http://gcc.gnu.org/ml/fortran/2009-04/msg00103.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39665

[Bug libfortran/39665] [4.5 Regression] Fortran IO using unaligned accesses to read/write doubles.

2009-04-09 Thread jb at gcc dot gnu dot org
--- Comment #10 from jb at gcc dot gnu dot org 2009-04-09 17:44 --- Subject: Bug 39665 Author: jb Date: Thu Apr 9 17:44:23 2009 New Revision: 145852 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145852 Log: 2009-04-09 Janne Blomqvist PR fortran/39665

[Bug libfortran/39702] [4.5 Regression] Unaligned access in Fortran testcases

2009-04-09 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2009-04-09 21:14 --- HJ, can you check if the patch at http://gcc.gnu.org/ml/fortran/2009-04/msg00103.html fixes your problems? It is the alternative way of solving the problem that IMHO was not as clean as r145852, but if that one

[Bug libfortran/39665] [4.5 Regression] Fortran IO using unaligned accesses to read/write doubles.

2009-04-10 Thread jb at gcc dot gnu dot org
--- Comment #11 from jb at gcc dot gnu dot org 2009-04-10 07:23 --- Subject: Bug 39665 Author: jb Date: Fri Apr 10 07:23:25 2009 New Revision: 145875 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145875 Log: 2009-04-10 Janne Blomqvist PR libfortran/39665 li

[Bug libfortran/39665] [4.5 Regression] Fortran IO using unaligned accesses to read/write doubles.

2009-04-13 Thread jb at gcc dot gnu dot org
--- Comment #12 from jb at gcc dot gnu dot org 2009-04-13 16:55 --- Fixed as of r145875 -- jb at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug c/38688] __sync_lock_test_and_set does not actually lock

2009-04-15 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2009-04-15 19:38 --- Subject: Bug 38688 Author: jb Date: Wed Apr 15 19:38:32 2009 New Revision: 146134 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=146134 Log: 2009-04-15 Janne Blomqvist PR libfortr

[Bug c/38688] __sync_lock_test_and_set does not actually lock

2009-04-15 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2009-04-15 19:42 --- Er, sorry, wrong PR in the ChangeLog. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38688

[Bug libfortran/38668] advance="no": no buffering, truncate and seek

2009-04-15 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2009-04-15 19:46 --- Fixed in trunk as r146134 & r146135. -- jb at gcc dot gnu dot org changed: What|Removed |A

[Bug fortran/31243] truncating strings longer than 2**32 characters

2009-04-17 Thread jb at gcc dot gnu dot org
--- Comment #6 from jb at gcc dot gnu dot org 2009-04-17 22:13 --- I'm not sure how this could be fixed in a "proper way" without breaking the procedure call ABI. Gfortran follows pretty much every other Fortran compiler in providing character length as a hidden argument

[Bug fortran/39667] I/O possibly unneccesary truncations

2009-04-17 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2009-04-17 22:18 --- Confirmed, assigning to myself. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/39782] [4.3/4.4/4.5 Regression] IO depends on uninitialised value

2009-04-18 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2009-04-18 10:05 --- Subject: Bug 39782 Author: jb Date: Sat Apr 18 10:05:34 2009 New Revision: 146308 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=146308 Log: 2009-04-18 Janne Blomqvist PR libfortr

[Bug fortran/39782] [4.3/4.4 Regression] IO depends on uninitialised value

2009-04-22 Thread jb at gcc dot gnu dot org
--- Comment #8 from jb at gcc dot gnu dot org 2009-04-22 21:37 --- Having a shot at backporting, assigning to myself. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/39667] I/O possibly unneccesary truncations

2009-04-30 Thread jb at gcc dot gnu dot org
--- Comment #2 from jb at gcc dot gnu dot org 2009-04-30 15:12 --- Subject: Bug 39667 Author: jb Date: Thu Apr 30 15:12:37 2009 New Revision: 147004 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=147004 Log: Fix PR libfortran/39667 Modified: trunk/gcc/testsuite/C

[Bug libfortran/40863] [4.5 Regression] Build failure in libgfortran

2009-08-14 Thread jb at gcc dot gnu dot org
--- Comment #12 from jb at gcc dot gnu dot org 2009-08-14 17:45 --- Subject: Bug 40863 Author: jb Date: Fri Aug 14 17:44:50 2009 New Revision: 150765 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150765 Log: PR libfortran/40863 Fix r150107 moving new symbols to C99_

[Bug fortran/39667] I/O possibly unneccesary truncations

2009-08-25 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2009-08-25 22:17 --- Updated patch fixing remaining fd_truncate issues with testsuite. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/39667] I/O possibly unneccesary truncations

2009-08-27 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2009-08-27 17:41 --- Subject: Bug 39667 Author: jb Date: Thu Aug 27 17:40:55 2009 New Revision: 151144 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=151144 Log: PR libfortran/39667 Fix testcases to not need fd_truncate.

[Bug fortran/39667] I/O possibly unneccesary truncations

2009-08-28 Thread jb at gcc dot gnu dot org
--- Comment #6 from jb at gcc dot gnu dot org 2009-08-28 14:48 --- Closing as fixed -- jb at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug fortran/41219] libgfortran build warnings

2009-09-06 Thread jb at gcc dot gnu dot org
--- Comment #6 from jb at gcc dot gnu dot org 2009-09-06 13:55 --- (In reply to comment #2) > Janne, I think the warning about "unix.c:750:15: warning: ‘statbuf.st_mode’ > may > be used uninitialized" is spurious, but can you have a look? Yes, it's spurious,

[Bug fortran/25829] [F2003] Asynchronous IO support

2009-10-28 Thread jb at gcc dot gnu dot org
--- Comment #13 from jb at gcc dot gnu dot org 2009-10-28 22:03 --- Reassigning to myself, I have a plan how to proceed with supporting proper async I/O in the library. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41860] New: -finit-local-XXX clobbers -fno-automatic

2009-10-28 Thread jb at gcc dot gnu dot org
AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41860

[Bug fortran/41860] -finit-local-XXX clobbers -fno-automatic

2009-10-28 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2009-10-28 23:25 --- Subject: Bug 41860 Author: jb Date: Wed Oct 28 23:25:08 2009 New Revision: 153689 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=153689 Log: PR fortran/41860 Treat vars as save with -fno-automatic

[Bug fortran/41860] -finit-local-XXX clobbers -fno-automatic

2009-10-28 Thread jb at gcc dot gnu dot org
-- jb at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jb at gcc dot gnu dot org |dot org

[Bug fortran/41219] libgfortran build warnings

2009-10-30 Thread jb at gcc dot gnu dot org
--- Comment #21 from jb at gcc dot gnu dot org 2009-10-30 22:37 --- Subject: Bug 41219 Author: jb Date: Fri Oct 30 22:37:47 2009 New Revision: 153769 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=153769 Log: PR libfortran/41219 Fix build warnings Modified:

[Bug middle-end/31738] New: Fortran dot product vectorization is restricted

2007-04-28 Thread jb at gcc dot gnu dot org
Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31738

[Bug fortran/31016] Use __buildin_memcpy and __memcpy for array assignment

2007-04-29 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2007-04-29 11:46 --- I don't think you can use memset for populating real arrays except when the value is 0.0; the bit patterns would be different, as memset takes an int argument which is actually converted to unsigned char. AFAIK the

[Bug middle-end/31750] New: Suboptimal builtin_memset on x86 with SSE

2007-04-29 Thread jb at gcc dot gnu dot org
Keywords: missed-optimization Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31750

[Bug middle-end/31750] Suboptimal builtin_memset on x86 with SSE

2007-04-29 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2007-04-29 12:14 --- Jakub made a related patch a while ago: http://gcc.gnu.org/ml/gcc-patches/2006-08/msg01134.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31750

[Bug tree-optimization/31762] New: ICE in tree-dfa.c:791 with -ftree-loop-linear (and -O1 -ffast-math)

2007-04-29 Thread jb at gcc dot gnu dot org
.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31762

[Bug middle-end/31750] Suboptimal builtin_memset on x86 with SSE

2007-04-29 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-04-29 20:19 --- Hmm, try e.g. the following (with gfortran the fixed sized arrays can use builtin_memset whereas the allocatable arrays are done with a loop. Save as .F90 (capital F) to force preprocessing to set the SZ macro. ! Test

[Bug libfortran/31933] Uninitialized memory when writing real(10) as unformatted

2007-05-18 Thread jb at gcc dot gnu dot org
--- Comment #1 from jb at gcc dot gnu dot org 2007-05-18 20:07 --- Seems to work fine on i686-pc-linux-gnu. I would have guessed it to be something related to padding, but it's weird that it's not seen in 32-bit mode. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31933

[Bug libfortran/31297] Use of uninitialized variables in libgfortran's I/O

2007-05-18 Thread jb at gcc dot gnu dot org
--- Comment #7 from jb at gcc dot gnu dot org 2007-05-18 20:52 --- Seems unf_io_convert_3.f90 is fixed by the patch for PR31915, which adds padding for CONVERT. The patch was committed as r124741. Closing, please verify and reopen if I'm wrong. -- jb at gcc dot gnu dot org ch

[Bug fortran/31067] MINLOC should sometimes be inlined (gas_dyn is sooooo sloooow)

2007-05-18 Thread jb at gcc dot gnu dot org
--- Comment #16 from jb at gcc dot gnu dot org 2007-05-18 21:15 --- The critical thing with inlining array intrinsics, IMHO is to give the optimizer more data to work with allowing it to get rid of temp arrays, perform loop fusion or fission etc. So with a trivial benchmark like #15

[Bug fortran/31067] MINLOC should sometimes be inlined (gas_dyn is sooooo sloooow)

2007-05-18 Thread jb at gcc dot gnu dot org
--- Comment #17 from jb at gcc dot gnu dot org 2007-05-18 21:20 --- Or even better (duh): REAL :: DTEMP DT = HUGE(1.0d0) DO I = 1, NODES DTEMP = DX(I)/(ABS(VEL(I)+SOUND(I)) IF (DTEMP < DT) THEN DT = DTEMP END IF END DO -- http://gcc.gnu.org/bugzi

[Bug middle-end/31066] Suboptimal vectorization after inlining

2007-05-18 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-05-18 22:11 --- Closing as invalid. gfortran vectorizes the loop in gas_dyn:eos as it should. The real reason why gfortran sucks at gas_dyn is that ifort uses the reciprocal approximation instructions and a Newton-Rhapson step instead

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

2007-05-19 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2007-05-19 17:51 --- There are enough pitfalls with using rdtsc that I don't think it's justifiable to use it for a general purpose timing routine like system_clock. See e.g.: http://www.ussg.iu.edu/hypermail/linux/kernel/0505.1

[Bug libfortran/31933] Uninitialized memory when writing real(10) as unformatted

2007-05-20 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-05-20 09:46 --- I see. With that in mind, I think the patch for PR31915 that went in as r124741 is incorrect (and I share some of the blame since I approved it). We should use the size argument the frontend provides to the unformatted_

[Bug libfortran/31933] Uninitialized memory when writing real(10) as unformatted

2007-05-20 Thread jb at gcc dot gnu dot org
--- Comment #4 from jb at gcc dot gnu dot org 2007-05-20 09:50 --- (In reply to comment #3) > I see. With that in mind, I think the patch for PR31915 that went in as > r124741 > is incorrect (and I share some of the blame since I approved it). We should > use > the si

[Bug libfortran/31933] Uninitialized memory when writing real(10) as unformatted

2007-05-21 Thread jb at gcc dot gnu dot org
--- Comment #7 from jb at gcc dot gnu dot org 2007-05-22 06:52 --- (In reply to comment #6) > The following simplistic patch solves this problem. Sometimes I think we get > overzealous with definitions and fancy configury. We all know the size is 10 > bytes and 12 works. No

[Bug fortran/32131] knowing that stride==1 when using allocated arrays and escaping allocatable arrays

2007-05-28 Thread jb at gcc dot gnu dot org
--- Comment #2 from jb at gcc dot gnu dot org 2007-05-29 04:30 --- PR31738 is another "missed vectorization in Fortran", though I don't think it's really that related to this one. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32131

[Bug fortran/32131] knowing that stride==1 when using allocated arrays and escaping allocatable arrays

2007-05-29 Thread jb at gcc dot gnu dot org
--- Comment #6 from jb at gcc dot gnu dot org 2007-05-29 17:51 --- Reopening. This vectorizes only partly, with -ffast-math to boot. We should be able to vectorize it without doing any "unsafe" math. gfortran -O2 -ffast-math -march=native -mfpmath=sse -ftree-vectorize -ftree-

[Bug middle-end/31723] Use reciprocal and reciprocal square root with -ffast-math

2007-06-10 Thread jb at gcc dot gnu dot org
--- Comment #13 from jb at gcc dot gnu dot org 2007-06-10 11:06 --- (In reply to comment #11) Thanks for the work. > First, please note that "divss" instruction is quite _fast_, clocking at 23 > cycles, where approximation with NR step would sum up to 20 cycles, not &g

[Bug fortran/32239] optimize power in loops, use __builtin_powi instead of _gfortran_pow_r4_i4

2007-06-16 Thread jb at gcc dot gnu dot org
--- Comment #2 from jb at gcc dot gnu dot org 2007-06-17 06:39 --- Assigning to myself, this should be easy to fix. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug middle-end/32503] __builtin_powi - optimize for other exponents besides 2 and 0.5

2007-06-26 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2007-06-26 19:00 --- (In reply to comment #2) > Confirmed. I had done tree-level expansion of powi into add/mul sequences at > one time. But this had been rejected for some reason I cannot remember right > now. The middle-end i

[Bug fortran/31067] MINLOC should sometimes be inlined (gas_dyn is sooooo sloooow)

2007-06-27 Thread jb at gcc dot gnu dot org
--- Comment #19 from jb at gcc dot gnu dot org 2007-06-27 14:49 --- gfortran does inline most array intrinsics, but only if the result is a scalar. For most array intrinsics this isn't that much of a problem since usually one uses the variant that returns a scalar, but MINL

[Bug fortran/32131] knowing that stride==1 when using allocated arrays and escaping allocatable arrays

2007-06-27 Thread jb at gcc dot gnu dot org
--- Comment #7 from jb at gcc dot gnu dot org 2007-06-27 15:56 --- (In reply to comment #5) > I can see two ways to address this issue (both of them worth pursuing): > > a) For allocatable arrays, we can always assume stride=1. But this helps only locally in the procedure

[Bug fortran/32239] optimize power in loops, use __builtin_powi instead of _gfortran_pow_r4_i4

2007-07-01 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2007-07-01 16:24 --- Subject: Bug 32239 Author: jb Date: Sun Jul 1 16:24:38 2007 New Revision: 126175 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126175 Log: gcc/fortran: 2007-07-01 Janne Blomqvist <[EMAI

[Bug fortran/32239] optimize power in loops, use __builtin_powi instead of _gfortran_pow_r4_i4

2007-07-02 Thread jb at gcc dot gnu dot org
--- Comment #6 from jb at gcc dot gnu dot org 2007-07-02 16:21 --- Subject: Bug 32239 Author: jb Date: Mon Jul 2 16:21:37 2007 New Revision: 126215 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126215 Log: Forgot to delete these during yesterdays commit. 2007-07-0

[Bug fortran/32239] optimize power in loops, use __builtin_powi instead of _gfortran_pow_r4_i4

2007-07-02 Thread jb at gcc dot gnu dot org
--- Comment #7 from jb at gcc dot gnu dot org 2007-07-02 20:46 --- Closing as Fortran FE is fixed. There is 32503 for better vectorization of builtin_powi, and if we want the strength reduction optimization from comment #0 a new missed-optimization PR should be filed against the middle

[Bug target/43481] huge object files generated for un-initialized data

2010-03-22 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2010-03-22 16:51 --- Seems to be a target bug, nothing to do with the Fortran frontend. Also, unless "turley" has a copyright assignment on file with the FSF (didn't find him/her in the MAINTAINERS file), the patch unfortun

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-03-31 Thread jb at gcc dot gnu dot org
--- Comment #3 from jb at gcc dot gnu dot org 2010-03-31 15:38 --- Assigning to myself. This is probably due to ftell not taking into account fbuf. -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-03-31 Thread jb at gcc dot gnu dot org
--- Comment #5 from jb at gcc dot gnu dot org 2010-03-31 18:42 --- Patch: http://gcc.gnu.org/ml/gcc-patches/2010-03/msg01523.html -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #8 from jb at gcc dot gnu dot org 2010-04-01 08:55 --- (In reply to comment #7) > I can confirm that the patch works for both the "(a)" and the "*" case. Thanks for testing. I'll commit the patch to 4.5 tonight. > In the code, there is stil

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #9 from jb at gcc dot gnu dot org 2010-04-01 16:23 --- Subject: Bug 43605 Author: jb Date: Thu Apr 1 16:22:57 2010 New Revision: 157914 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157914 Log: PR libfortran/43605 Fix FTELL for formatted files Added:

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #10 from jb at gcc dot gnu dot org 2010-04-01 16:31 --- Subject: Bug 43605 Author: jb Date: Thu Apr 1 16:31:01 2010 New Revision: 157915 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157915 Log: PR libfortran/43605 FTELL incorrect for formatted files

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #11 from jb at gcc dot gnu dot org 2010-04-01 16:34 --- Fixed, closing. -- jb at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #14 from jb at gcc dot gnu dot org 2010-04-01 19:45 --- (In reply to comment #13) > (In reply to comment #12) > > > >0 > > '123456' > >7 > > 'D' > > 113 > > >

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #16 from jb at gcc dot gnu dot org 2010-04-01 20:27 --- Patch, take 2: http://gcc.gnu.org/ml/gcc-patches/2010-04/msg00072.html -- jb at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/43605] [4.4/4.5 Regression] wrong results with ftell

2010-04-01 Thread jb at gcc dot gnu dot org
--- Comment #19 from jb at gcc dot gnu dot org 2010-04-01 20:52 --- Subject: Bug 43605 Author: jb Date: Thu Apr 1 20:51:45 2010 New Revision: 157932 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157932 Log: PR libfortran/43605 FTELL intrinsic, take 2. Modified: t

<    1   2   3   >