[Bug fortran/48636] Enable more inlining with -O2 and higher

2011-04-20 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48636 --- Comment #11 from Janne Blomqvist 2011-04-20 18:14:20 UTC --- (In reply to comment #9) > > But do we actually do this? I did some tests a while ago, and IIRC for > > assumed > > shape dummy arguments the procedure always calculates new bounds

[Bug libfortran/25830] [libgfortran] Optionally support multi-process locking

2011-04-25 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25830 --- Comment #4 from Janne Blomqvist 2011-04-25 16:41:26 UTC --- Some writings arguing that POSIX locking is more or less fundamentally broken: http://0pointer.de/blog/projects/locking.html http://0pointer.de/blog/projects/locking2.html http://

[Bug libfortran/48511] Implement Steele-White algorithm for numeric output

2011-04-27 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48511 --- Comment #9 from Janne Blomqvist 2011-04-27 18:36:12 UTC --- I've been thinking about this issue now and then over the past few weeks, and funnily enough, while I initially thought this would be a nice improvement, I've subsequently come to th

[Bug libfortran/48511] Implement Steele-White algorithm for numeric output

2011-04-28 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48511 --- Comment #10 from Janne Blomqvist 2011-04-28 09:30:10 UTC --- As an addendum to the above, one thing we could do with modest effort and without importing Gay's code would be to remove trailing zeros for G0 (and maybe list directed) output.

[Bug libfortran/48488] Wrong default format for real numbers

2011-04-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48488 --- Comment #6 from Janne Blomqvist 2011-04-29 15:58:23 UTC --- Author: jb Date: Fri Apr 29 15:58:20 2011 New Revision: 173169 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173169 Log: PR 48488 Fix comments Modified: trunk/libgfortr

[Bug libfortran/48488] Wrong default format for real numbers

2011-04-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48488 --- Comment #8 from Janne Blomqvist 2011-04-29 16:06:55 UTC --- Author: jb Date: Fri Apr 29 16:06:48 2011 New Revision: 173171 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173171 Log: PR 48488 Typo Modified: trunk/libgfortran/io/wr

[Bug libfortran/48488] Wrong default format for real numbers

2011-04-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48488 --- Comment #7 from Janne Blomqvist 2011-04-29 16:03:57 UTC --- Author: jb Date: Fri Apr 29 16:03:54 2011 New Revision: 173170 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173170 Log: PR 48488 Fix comments Modified: trunk/libgfortr

[Bug c/48874] New: Sign of zeros sometimes lost in literals

2011-05-04 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48874 Summary: Sign of zeros sometimes lost in literals Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassig...@

[Bug c/48874] Sign of zeros sometimes lost in literals

2011-05-04 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48874 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

2011-05-04 Thread jb at gcc dot gnu.org
||2011.05.04 20:38:38 CC||jb at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #1 from Janne Blomqvist 2011-05-04 20:38:38 UTC --- Confirmed. Wrt the space wastage, gfortran uses fixed width fields for each

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

2011-05-04 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #3 from Janne Blomqvist 2011-05-05 03:33:30 UTC --- (In reply to comment #2) > We have another PR in place that is related to this, pr31190 Thanks for the reminder. > One thought was to hide this behind an option so that one could s

[Bug libfortran/48878] New: Default I/O rounding on output should be round to nearest

2011-05-04 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48878 Summary: Default I/O rounding on output should be round to nearest Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

2011-05-05 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #5 from Janne Blomqvist 2011-05-05 12:11:02 UTC --- (In reply to comment #4) > (In reply to comment #3) > > neither 0PFw.d nor 1PEw.dEe allow it). However, AFAICS leading blanks are > > still > > allowed as they are part of the real

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

2011-05-05 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #7 from Janne Blomqvist 2011-05-05 12:44:42 UTC --- (In reply to comment #6) > On 05/05/2011 12:04 AM, thenlich at users dot sourceforge.net wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 > ---snip--- > > As much as I'd

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-06 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 --- Comment #1 from Janne Blomqvist 2011-05-06 11:31:38 UTC --- Assigning to myself, I have some ideas to improve error handling and fix this in the process.

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-06 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 Janne Blomqvist changed: What|Removed |Added AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org

[Bug libfortran/48915] New: Incorrect process return code with -fdump-core

2011-05-06 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 Summary: Incorrect process return code with -fdump-core Product: gcc Version: unknown Status: UNCONFIRMED Severity: minor Priority: P3 Component: libfortran AssignedT

[Bug libfortran/48931] New: Backtrace functionality not async-signal-safe

2011-05-08 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931 Summary: Backtrace functionality not async-signal-safe Product: gcc Version: unknown Status: UNCONFIRMED Severity: minor Priority: P3 Component: libfortran AssignedTo

[Bug fortran/38199] missed optimization: I/O performance

2011-05-10 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38199 --- Comment #13 from Janne Blomqvist 2011-05-10 09:41:08 UTC --- Here's something for formatted writes; consider the write-many.f (from some other PR, I'm too lazy to check which now) program main open(10,status='SCRATCH') a = 0.3858204 do

[Bug fortran/48972] OPEN with Unicode file name

2011-05-12 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48972 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #3

[Bug fortran/48972] OPEN with Unicode file name

2011-05-12 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48972 --- Comment #8 from Janne Blomqvist 2011-05-12 21:02:40 UTC --- (In reply to comment #4) > (In reply to comment #3) > > - Specify that the default character set is UTF-8. > > What do you mean by that? I know 1 byte and 4 byte character variables

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-14 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 --- Comment #3 from Janne Blomqvist 2011-05-14 08:44:12 UTC --- Author: jb Date: Sat May 14 08:44:09 2011 New Revision: 173750 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173750 Log: PR 48915 Abort handling Modified: trunk/gcc/for

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-14 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-14 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 --- Comment #5 from Janne Blomqvist 2011-05-14 10:20:59 UTC --- Author: jb Date: Sat May 14 10:20:56 2011 New Revision: 173753 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173753 Log: PR 48915 Update mixed-language programming documenta

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-14 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 --- Comment #6 from Janne Blomqvist 2011-05-14 10:24:20 UTC --- Author: jb Date: Sat May 14 10:24:18 2011 New Revision: 173754 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173754 Log: PR 48915 Update mixed-language programming documenta

[Bug libfortran/48931] Backtrace functionality not async-signal-safe

2011-05-14 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931 Janne Blomqvist changed: What|Removed |Added AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org

[Bug libfortran/48931] Backtrace functionality not async-signal-safe

2011-05-15 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931 Janne Blomqvist changed: What|Removed |Added URL||http://gcc.gnu.org/ml/gcc-p

[Bug libfortran/48915] Incorrect process return code with -fdump-core

2011-05-15 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48915 --- Comment #7 from Janne Blomqvist 2011-05-15 10:23:56 UTC --- Author: jb Date: Sun May 15 10:23:53 2011 New Revision: 173770 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173770 Log: PR 48915 Clarify _gfortran_set_options documentation

[Bug fortran/49010] Result of MOD and MODULO intrinsic has wrong sign

2011-05-17 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49010 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #6

[Bug fortran/49010] Result of MOD and MODULO intrinsic has wrong sign

2011-05-17 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49010 --- Comment #8 from Janne Blomqvist 2011-05-17 14:02:07 UTC --- So does the fallback path actually ever get used? AFAICS the builtins are always available, and if the builtin results in a call to fmod{f,,l,Q} we have fallback implementations in c

[Bug fortran/49010] Result of MOD and MODULO intrinsic has wrong sign

2011-05-17 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49010 --- Comment #11 from Janne Blomqvist 2011-05-17 16:18:41 UTC --- (In reply to comment #10) > On Tue, May 17, 2011 at 02:17:22PM +0000, jb at gcc dot gnu.org wrote: > > > > So does the fallback path actually ever get used? AFAICS t

[Bug fortran/49052] i386 version of gcc-4.5 fails to compile C or Fortran files on CIFS mounts

2011-05-19 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49052 --- Comment #3 from Janne Blomqvist 2011-05-19 09:01:30 UTC --- Not a GCC bug. As an aside, CIFS mounts work quite well IF the server supports the "CIFS Unix extensions"; Samba supports those, but IIRC the Windows CIFS server doesn't. Without t

[Bug libfortran/48982] libgfortran on sysv never uses fpsetmask

2011-05-20 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48982 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #2

[Bug fortran/48977] -fpe-trap=denormal on x86 GLIBC systems

2011-05-20 Thread jb at gcc dot gnu.org
gcc dot gnu.org AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #2 from Janne Blomqvist 2011-05-20 13:29:10 UTC --- Patch: http://gcc.gnu.org/ml/gcc-patches/2011

[Bug libfortran/48982] libgfortran on sysv never uses fpsetmask

2011-05-20 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48982 --- Comment #3 from Janne Blomqvist 2011-05-20 13:40:47 UTC --- Actually, in the version control log for acinclude.m4 we have commit b00fa2cfbfd81cbdc31d5a44e4ce8140cc153776 Author: fxcoudert Date: Fri Feb 25 17:56:04 2011 + * ac

[Bug libfortran/48982] libgfortran on sysv never uses fpsetmask

2011-05-20 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48982 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug fortran/48977] -fpe-trap=denormal on x86 GLIBC systems

2011-05-20 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48977 Janne Blomqvist changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug fortran/48977] -fpe-trap=denormal on x86 GLIBC systems

2011-05-20 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48977 --- Comment #3 from Janne Blomqvist 2011-05-20 14:45:53 UTC --- Author: jb Date: Fri May 20 14:45:51 2011 New Revision: 173952 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173952 Log: PR 48977 Denormal exception on glibc targets Modifi

[Bug libfortran/48931] Backtrace functionality not async-signal-safe

2011-05-22 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931 --- Comment #3 from Janne Blomqvist 2011-05-22 16:38:08 UTC --- Author: jb Date: Sun May 22 16:38:05 2011 New Revision: 174030 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174030 Log: PR 48931 Make backtrace async-signal-safe, reformat

[Bug libfortran/48931] Backtrace functionality not async-signal-safe

2011-05-22 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]

2010-10-16 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45629 --- Comment #1 from Janne Blomqvist 2010-10-16 22:07:19 UTC --- Created attachment 22068 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22068 Preliminary patch Preliminary patch for getting rid of setjmp/longjmp, instead using an errno-styl

[Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]

2010-10-16 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45629 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org

[Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]

2010-11-01 Thread jb at gcc dot gnu.org
||2010.11.01 07:28:21 AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #4 from Janne Blomqvist 2010-11-01 07:28:21 UTC --- Scratch that previous

[Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]

2010-11-01 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45629 Janne Blomqvist changed: What|Removed |Added URL||http://gcc.gnu.org/ml/gcc-p

[Bug libfortran/46267] New: strerror() is not necessarily thread-safe

2010-11-02 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267 Summary: strerror() is not necessarily thread-safe Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: una

[Bug middle-end/35877] difference between result in optimized and normal executable

2010-11-02 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35877 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]

2010-11-02 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45629 --- Comment #6 from Janne Blomqvist 2010-11-02 12:56:44 UTC --- Author: jb Date: Tue Nov 2 12:56:38 2010 New Revision: 166180 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166180 Log: PR 45629 Remove usage of setjmp/longjmp Modified:

[Bug libfortran/46267] strerror() is not necessarily thread-safe

2010-11-02 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46267 --- Comment #3 from Janne Blomqvist 2010-11-02 13:20:48 UTC --- Well, if we want to use strerror_r() we'd have to either first undef _GNU_SOURCE before we include string.h so that we get the POSIX version (but, might this cause some other weird b

[Bug fortran/43849] Add _gfortran_finalize function to close down the library

2010-11-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43849 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #3

[Bug fortran/44931] For INPUT_UNIT, INQUIRE NAME= should not return "stdin"

2010-11-04 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44931 --- Comment #14 from Janne Blomqvist 2010-11-04 19:29:33 UTC --- Author: jb Date: Thu Nov 4 19:29:28 2010 New Revision: 166325 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166325 Log: PR 44931 Move struct unix_stream to unix.c Modifie

[Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]

2010-11-04 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45629 Janne Blomqvist changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug fortran/28105] Check for memory allocations bigger than size_t

2010-11-19 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28105 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org

[Bug fortran/28105] Check for memory allocations bigger than size_t

2010-11-22 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28105 Janne Blomqvist changed: What|Removed |Added URL||http://gcc.gnu.org/ml/gcc-p

[Bug fortran/28105] Check for memory allocations bigger than size_t

2010-11-30 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28105 --- Comment #6 from Janne Blomqvist 2010-11-30 21:33:36 UTC --- Author: jb Date: Tue Nov 30 21:33:32 2010 New Revision: 167317 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167317 Log: PR fortran/28105 Overflow check for ALLOCATE stateme

[Bug fortran/28105] Check for memory allocations bigger than size_t

2010-12-01 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28105 --- Comment #8 from Janne Blomqvist 2010-12-01 14:43:55 UTC --- AFAICS the patch I committed in #6 as r167317 only changes how the ALLOCATE statement is compiled. For automatic and static arrays, different codepaths are chosen. In principle we

[Bug fortran/46945] [4.6 Regression] gfortran.dg/unpack_zerosize_1.f90 FAILs with -ftree-vrp -fno-tree-ccp -fno-tree-fre

2010-12-15 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46945 --- Comment #3 from Janne Blomqvist 2010-12-15 11:57:28 UTC --- The offending patch is most likely http://gcc.gnu.org/ml/gcc-patches/2010-11/msg02499.html Wrt. the recent changes in the definition of size_t, there is http://gcc.gnu.org/ml/gcc-

[Bug fortran/28105] Check for memory allocations bigger than size_t

2010-12-15 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28105 --- Comment #11 from Janne Blomqvist 2010-12-15 17:15:31 UTC --- Author: jb Date: Wed Dec 15 17:15:25 2010 New Revision: 167860 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167860 Log: PR 28105 Remove size<0 checks before calling malloc

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

2011-05-28 Thread jb at gcc dot gnu.org
://gcc.gnu.org/ml/fortr |http://gcc.gnu.org/ml/gcc-p |an/2005-06/msg00318.html|atches/2011-05/msg02224.htm ||l CC||jb at gcc dot gnu.org Resolution|FIXED

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

2011-05-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19155 --- Comment #28 from Janne Blomqvist 2011-05-29 08:59:47 UTC --- Author: jb Date: Sun May 29 08:59:44 2011 New Revision: 174393 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174393 Log: PR 19155 Check for strtod failure via endptr Modif

[Bug libfortran/48982] libgfortran on sysv never uses fpsetmask

2011-05-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48982 Janne Blomqvist changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|

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

2011-05-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19155 Janne Blomqvist changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

[Bug libfortran/49214] [4.7 Regression] Broken pipe in backtrace for x86_64-apple-darwin10

2011-05-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49214 --- Comment #3 from Janne Blomqvist 2011-05-29 13:17:20 UTC --- Author: jb Date: Sun May 29 13:17:17 2011 New Revision: 174395 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174395 Log: PR 49214 fd_gets should return NULL if nothing was r

[Bug libfortran/48931] Backtrace functionality not async-signal-safe

2011-05-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48931 --- Comment #5 from Janne Blomqvist 2011-05-29 20:13:56 UTC --- Author: jb Date: Sun May 29 20:13:52 2011 New Revision: 174415 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174415 Log: PR 48931 Use async-signal-safe execve instead of exe

[Bug libfortran/49214] [4.7 Regression] Broken pipe in backtrace for x86_64-apple-darwin10

2011-05-29 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49214 Janne Blomqvist changed: What|Removed |Added Target Milestone|4.7.0 |--- --- Comment #5 from Janne Blomqvist

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-06-11 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 Janne Blomqvist changed: What|Removed |Added AssignedTo|unassigned at gcc dot |jb at gcc dot gnu.org

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-06-17 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 Janne Blomqvist changed: What|Removed |Added URL||http://gcc.gnu.org/ml/gcc-p

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-06-18 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #10 from Janne Blomqvist 2011-06-18 07:53:12 UTC --- Author: jb Date: Sat Jun 18 07:53:09 2011 New Revision: 175166 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175166 Log: PR 49296 List directed read of string ending in EOF

[Bug c++/48296] [C++0x] constexpr member function cannot use the class type it belongs as parameter type or return type

2011-06-18 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48296 --- Comment #5 from Janne Blomqvist 2011-06-18 07:53:12 UTC --- Author: jb Date: Sat Jun 18 07:53:09 2011 New Revision: 175166 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175166 Log: PR 49296 List directed read of string ending in EOF.

[Bug c++/48296] [C++0x] constexpr member function cannot use the class type it belongs as parameter type or return type

2011-07-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48296 --- Comment #6 from Janne Blomqvist 2011-07-03 15:54:05 UTC --- Author: jb Date: Sun Jul 3 15:54:02 2011 New Revision: 175787 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175787 Log: PR 48296 Accept EOF as separator when reading string

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #12 from Janne Blomqvist 2011-07-03 15:54:05 UTC --- Author: jb Date: Sun Jul 3 15:54:02 2011 New Revision: 175787 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175787 Log: PR 48296 Accept EOF as separator when reading strin

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #13 from Janne Blomqvist 2011-07-03 16:00:34 UTC --- Author: jb Date: Sun Jul 3 16:00:32 2011 New Revision: 175788 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175788 Log: PR 49296 Fix wrong PR number in ChangeLog entry Mo

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #14 from Janne Blomqvist 2011-07-03 17:37:33 UTC --- Author: jb Date: Sun Jul 3 17:37:30 2011 New Revision: 175789 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175789 Log: PR 49296 Fix wrong PR number in ChangeLog Modified

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #15 from Janne Blomqvist 2011-07-03 17:40:11 UTC --- Created attachment 24662 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24662 Updated testcase Updated testcase that checks integer, real, and logical types in addition to cha

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-13 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #16 from Janne Blomqvist 2011-07-13 18:46:48 UTC --- Author: jb Date: Wed Jul 13 18:46:44 2011 New Revision: 176245 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176245 Log: PR 49296 List read, EOF without preceding separator

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-13 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 --- Comment #17 from Janne Blomqvist 2011-07-13 18:52:43 UTC --- Author: jb Date: Wed Jul 13 18:52:40 2011 New Revision: 176246 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176246 Log: PR 49296 List read, EOF before separator, backport

[Bug libfortran/49296] [4.6/4.7 Regression] Wrong END OF FILE error for list-directed I/O with strings

2011-07-13 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49296 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug libfortran/50016] The fortran program 's io is very slow

2011-08-08 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50016 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #6

[Bug libfortran/52879] Pathological reseeding of PRNG generator genernates poor sequence

2016-08-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52879 --- Comment #5 from Janne Blomqvist --- To be honest, I'm not sure that this test program really tests anything sensible. There is no rule in the secret black book of PRNG algorithm design, nor in the Fortran standard, that generating a single va

[Bug libfortran/77261] gfortran.dg/random_3.f90 FAILs

2016-08-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77261 --- Comment #2 from Janne Blomqvist --- (In reply to Dominique d'Humieres from comment #1) > AFAIU this occurs for platforms without real(10) and is due to the fact that > the sequence for real(16) is different from the sequence for other reals.

[Bug libfortran/77261] gfortran.dg/random_3.f90 FAILs

2016-08-22 Thread jb at gcc dot gnu.org
|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org --- Comment #3 from Janne Blomqvist --- Assigning to myself.

[Bug libfortran/77261] gfortran.dg/random_3.f90 FAILs

2016-08-23 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77261 Janne Blomqvist changed: What|Removed |Added URL||https://gcc.gnu.org/ml/gcc-

[Bug libfortran/77261] gfortran.dg/random_3.f90 FAILs

2016-08-29 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77261 --- Comment #6 from Janne Blomqvist --- Author: jb Date: Mon Aug 29 08:29:16 2016 New Revision: 239817 URL: https://gcc.gnu.org/viewcvs?rev=239817&root=gcc&view=rev Log: PR fortran/77261 Run random_3 testcase only when real(10) is available. Mo

[Bug libfortran/103886] New: Use 64-bit time_t on 32-bit glibc targets

2022-01-01 Thread jb at gcc dot gnu.org via Gcc-bugs
Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- In order to solve the Y2038 problem glibc now supports 64-bit time_t on 32-bit platforms. As this is an ABI change, it has to be explicitly enabled through setting the

[Bug libfortran/103886] Use 64-bit time_t on 32-bit glibc targets

2022-01-01 Thread jb at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886 --- Comment #2 from Janne Blomqvist --- (In reply to Andrew Pinski from comment #1) > Is there anything to be done as the time_t is now defaults to 64bit on the > trunk of glibc? AFAIU it's not the default, you need to explicitly opt-in by sett

[Bug libfortran/103886] Use 64-bit time_t on 32-bit glibc targets

2022-01-01 Thread jb at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886 --- Comment #4 from Janne Blomqvist --- (In reply to Andrew Pinski from comment #3) > (In reply to Janne Blomqvist from comment #2) > > (In reply to Andrew Pinski from comment #1) > > > Is there anything to be done as the time_t is now defaults

[Bug libfortran/98507] timezone is incorrect on last day of year for "TZ" hours

2021-12-16 Thread jb at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98507 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #5

[Bug fortran/107373] Unexpected result with loop optimisation

2022-10-24 Thread jb at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107373 --- Comment #3 from Janne Blomqvist --- 63ee540430c3 might be related wrt fixing it?

[Bug fortran/108131] New: Incorrect bound calculation when bound intrinsic used in size expression

2022-12-15 Thread jb at gcc dot gnu.org via Gcc-bugs
: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- This is from https://stackoverflow.com/questions/74814027/where-to-report-possible-gfortran-compiler-bug . Consider program test

[Bug fortran/101632] NON_RECURSIVE procedure prefix is unsupported. F2018 defaults to recursive procedures.

2021-08-03 Thread jb at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101632 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org

[Bug fortran/90504] Improved NORM2 algorithm

2023-05-24 Thread jb at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90504 --- Comment #2 from Janne Blomqvist --- (In reply to anlauf from comment #1) > (In reply to Janne Blomqvist from comment #0) > > Hanson, Hopkins, Remark on Algorithm 539: A Modern Fortran Reference > > Implementation for Carefully Computing the E

<    2   3   4   5   6   7