[Bug libfortran/78833] Misleading IOMSG after failed WRITE(...,POS=) on unconnected formatted stream file

2016-12-17 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78833 --- Comment #3 from mecej4 at operamail dot com --- I understand what happens, and this is not a bug per se', but in normal usage the message wording can be confusing. During the second run, the OPEN fails because 'NEW' is specified and the file

[Bug libfortran/78833] Misleading IOMSG after failed WRITE(...,POS=) on unconnected formatted stream file

2016-12-16 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78833 --- Comment #1 from mecej4 at operamail dot com --- Created attachment 40349 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40349=edit Test program for reproducing bug in IOMSG Same source code as in main message, for your convenience.

[Bug libfortran/78833] New: Misleading IOMSG after failed WRITE(...,POS=) on unconnected formatted stream file

2016-12-16 Thread mecej4 at operamail dot com
Severity: normal Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: mecej4 at operamail dot com Target Milestone: --- The program below, when run with Gfortran 6.2, runs correctly the first time, and produces an output file

[Bug fortran/78676] [5/6/7 Regression] Optimizer bug with -ftree-vrp exposed by program with many bit operations

2016-12-05 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78676 --- Comment #7 from mecej4 at operamail dot com --- (In reply to Andrew Pinski from comment #3) > Try -fwrapv . Thanks! Using that flag with -O2 does make the program give correct results, but I am a little confused about what that flag d

[Bug fortran/78676] Optimizer bug exposed by program with many bit operations.

2016-12-04 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78676 --- Comment #2 from mecej4 at operamail dot com --- (In reply to Andrew Pinski from comment #1) > This sounds like overflows are happening. Overflow in fortran is undefined. Very much so, but integer overflow happens a lot in random num

[Bug fortran/78676] New: Optimizer bug exposed by program with many bit operations.

2016-12-04 Thread mecej4 at operamail dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: mecej4 at operamail dot com Target Milestone: --- Created attachment 40244 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40244=edit Test program to demonstrate bug; run with (i)

[Bug libfortran/78549] Very slow formatted internal file output

2016-11-29 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #6 from mecej4 at operamail dot com --- (In reply to Jerry DeLisle from comment #5) > > Can you explain what "Windows Subsystem for Linux (Ubuntu 14) on Windows-10" > is? Sorry if I created a bad portmanteau phras

[Bug libfortran/78549] Very slow formatted internal file output

2016-11-28 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #4 from mecej4 at operamail dot com --- (In reply to Jerry DeLisle from comment #3) > We cannot address the Windows(+Cygwin,Mingw,etc.) issues which have more to > do with the OS related layers I assume. > > I will se

[Bug libfortran/78549] Very slow formatted internal file output

2016-11-28 Thread mecej4 at operamail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #2 from mecej4 at operamail dot com --- Thanks, Martin. After posting, I found that I could add more add more attachments, but I was a bit worried that, as in other forums, the initial post could not be edited or modified. I presume

[Bug libfortran/78549] New: Very slow formatted internal file output

2016-11-27 Thread mecej4 at operamail dot com
: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: mecej4 at operamail dot com Target Milestone: --- Created attachment 40163 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40163=edit Program to demonstrate bug Formatted internal writes to a string variable are v