[Bug fortran/77505] Negative character length not treated as LEN=0

2016-11-25 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77505 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #8

[Bug fortran/78534] New: Use a larger integer type for character lengths on 64-bit targets

2016-11-25 Thread jb at gcc dot gnu.org
: enhancement Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- Currently GFortran uses a plain C int for character lengths. This prevents longer characters on 64-bit targets. We should change

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-11-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 Janne Blomqvist changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-11-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #4 from Janne Blomqvist --- Created attachment 40154 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40154&action=edit Preliminary patch Preliminary patch changing gfc_charlen_t from int to ptrdiff_t. Fails the char_result_8.f90

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-11-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #5 from Janne Blomqvist --- (In reply to Jakub Jelinek from comment #2) > So are you going to do everything that is in the wiki (or most of it)? > Also, I couldn't find in the list, I think some descriptor changes were > considered (t

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-11-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #7 from Janne Blomqvist --- (In reply to Jakub Jelinek from comment #6) > (In reply to Janne Blomqvist from comment #5) > > (In reply to Jakub Jelinek from comment #2) > > > So are you going to do everything that is in the wiki (or mo

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-11-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #9 from Janne Blomqvist --- (In reply to Dominique d'Humieres from comment #8) > Will it help for pr66310? Probably yes, to the extent that with 64-bit indices the repeat count can be a lot larger than you can afford to buy RAM. :)

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-11-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #11 from Janne Blomqvist --- (In reply to Dominique d'Humieres from comment #10) > BTW did you test the patch in comment 4 with -m32? No, though I did test by reverting the few lines changing the definitions of gfc_charlen_type_node

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2016-12-04 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 Janne Blomqvist changed: What|Removed |Added Attachment #40154|0 |1 is obsolete|

[Bug fortran/78757] New: ICE with function returning a pointer to a character

2016-12-09 Thread jb at gcc dot gnu.org
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- The following testcase causes an ICE when compiling with -O1 on x86_64-pc-linux-gnu on todays (2016-12-09) trunk: ! Reduced and modified from char_result_8.f90 ! { dg

[Bug fortran/78867] New: GFortran function returning string ICE with -flto

2016-12-19 Thread jb at gcc dot gnu.org
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- The following testcase fails when compiled with -flto. Enabling optimization makes it work, e.g. "-O1 -flto". ! { dg-do compile } ! { dg-options "-flto&

[Bug fortran/78867] [7 Regression] GFortran function returning string ICE with -flto

2016-12-19 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78867 --- Comment #2 from Janne Blomqvist --- (In reply to Dominique d'Humieres from comment #1) > This seems to be a regression between revisions r243624 (2016-12-13, > compiles) and r243765 (2016-12-16, ICE with -m32 or -m64). Thanks for quickly nar

[Bug fortran/78867] [7 Regression] GFortran function returning string ICE with -flto

2016-12-20 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78867 --- Comment #3 from Janne Blomqvist --- (In reply to Janne Blomqvist from comment #2) > (In reply to Dominique d'Humieres from comment #1) > > This seems to be a regression between revisions r243624 (2016-12-13, > > compiles) and r243765 (2016-12

[Bug fortran/78867] [7 Regression] GFortran function returning string ICE with -flto

2016-12-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78867 --- Comment #6 from Janne Blomqvist --- Ok, I think I figured it out; like Richard said, it's a missing DECL_EXPR issue. Patch incoming shortly.-

[Bug fortran/78867] [7 Regression] GFortran function returning string ICE with -flto

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

[Bug fortran/78867] [7 Regression] GFortran function returning string ICE with -flto

2016-12-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78867 --- Comment #8 from Janne Blomqvist --- Author: jb Date: Wed Dec 21 09:41:25 2016 New Revision: 243842 URL: https://gcc.gnu.org/viewcvs?rev=243842&root=gcc&view=rev Log: PR 78867 Function returning string ICE with -flto The fix for PR 78757 was

[Bug fortran/78757] [7 Regression] ICE with function returning a pointer to a character

2016-12-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78757 --- Comment #8 from Janne Blomqvist --- Author: jb Date: Wed Dec 21 09:41:25 2016 New Revision: 243842 URL: https://gcc.gnu.org/viewcvs?rev=243842&root=gcc&view=rev Log: PR 78867 Function returning string ICE with -flto The fix for PR 78757 was

[Bug fortran/78867] [7 Regression] GFortran function returning string ICE with -flto

2016-12-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78867 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2017-01-02 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #14 from Janne Blomqvist --- Author: jb Date: Mon Jan 2 20:00:18 2017 New Revision: 244003 URL: https://gcc.gnu.org/viewcvs?rev=244003&root=gcc&view=rev Log: PR 78534 Modify string copy to avoid -Wstringop-overflow warning When the

[Bug fortran/78976] [7 Regression] FAIL: gfortran.dg/dependency_49.f90 and gfortran.dg/transfer_intrinsic_1.f90

2017-01-03 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78976 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2017-01-03 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #16 from Janne Blomqvist --- Author: jb Date: Tue Jan 3 18:01:30 2017 New Revision: 244027 URL: https://gcc.gnu.org/viewcvs?rev=244027&root=gcc&view=rev Log: PR 78534 Revert r244011 r244011 caused regressions on 32-bit hosts. Remo

[Bug fortran/78976] [7 Regression] FAIL: gfortran.dg/dependency_49.f90 and gfortran.dg/transfer_intrinsic_1.f90

2017-01-03 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78976 --- Comment #3 from Janne Blomqvist --- Ugh, yeah. I had to revert the big patch, https://gcc.gnu.org/ml/gcc-patches/2017-01/msg00110.html, which also reverted the testcase fixes. I'll commit them separately.

[Bug fortran/78976] [7 Regression] FAIL: gfortran.dg/dependency_49.f90 and gfortran.dg/transfer_intrinsic_1.f90

2017-01-04 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78976 --- Comment #4 from Janne Blomqvist --- Author: jb Date: Wed Jan 4 08:06:54 2017 New Revision: 244048 URL: https://gcc.gnu.org/viewcvs?rev=244048&root=gcc&view=rev Log: PR 78796 Modify testcases due to gfc_trans_string_copy change As r244011 h

[Bug target/78796] TLS fails to link on aarch64 with -mcmodel=large

2017-01-04 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78796 --- Comment #10 from Janne Blomqvist --- Author: jb Date: Wed Jan 4 08:06:54 2017 New Revision: 244048 URL: https://gcc.gnu.org/viewcvs?rev=244048&root=gcc&view=rev Log: PR 78796 Modify testcases due to gfc_trans_string_copy change As r244011

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2017-01-04 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #17 from Janne Blomqvist --- Author: jb Date: Wed Jan 4 08:06:54 2017 New Revision: 244048 URL: https://gcc.gnu.org/viewcvs?rev=244048&root=gcc&view=rev Log: PR 78796 Modify testcases due to gfc_trans_string_copy change As r244011

[Bug fortran/66310] Problems with intrinsic repeat for large number of copies

2017-01-13 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310 --- Comment #16 from Janne Blomqvist --- Author: jb Date: Fri Jan 13 17:05:48 2017 New Revision: 28 URL: https://gcc.gnu.org/viewcvs?rev=28&root=gcc&view=rev Log: PR 78534 Change character length from int to size_t In order to handle la

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

2017-01-13 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #18 from Janne Blomqvist --- Author: jb Date: Fri Jan 13 17:05:48 2017 New Revision: 28 URL: https://gcc.gnu.org/viewcvs?rev=28&root=gcc&view=rev Log: PR 78534 Change character length from int to size_t In order to handle la

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

2017-10-02 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829 --- Comment #26 from Janne Blomqvist --- I though I wrote somewhere why I gave up on this, after thinking a lot about the problem in general. However, I can't find my writeup now, so I'll add a short version here so that others who are interested

[Bug sanitizer/82869] c_associated does not always give false for null pointers

2017-11-07 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82869 Janne Blomqvist changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org

[Bug sanitizer/82869] c_associated does not always give false for null pointers

2017-11-07 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82869 Janne Blomqvist changed: What|Removed |Added URL||https://gcc.gnu.org/ml/gcc-

[Bug sanitizer/82869] c_associated does not always give false for null pointers

2017-11-08 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82869 --- Comment #7 from Janne Blomqvist --- Author: jb Date: Wed Nov 8 11:51:00 2017 New Revision: 254526 URL: https://gcc.gnu.org/viewcvs?rev=254526&root=gcc&view=rev Log: PR 82869 Introduce logical_type_node and use it Earlier GFortran used to r

[Bug sanitizer/82869] c_associated does not always give false for null pointers

2017-11-08 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82869 --- Comment #8 from Janne Blomqvist --- Fixed on trunk. I'll wait a few days for possible fallout and then backport it to the GCC-7 release as well.

[Bug sanitizer/82869] c_associated does not always give false for null pointers

2017-11-13 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82869 --- Comment #9 from Janne Blomqvist --- Author: jb Date: Mon Nov 13 20:01:20 2017 New Revision: 254706 URL: https://gcc.gnu.org/viewcvs?rev=254706&root=gcc&view=rev Log: Introduce logical_type_node and use it Backport from trunk. Earlier GFort

[Bug sanitizer/82869] c_associated does not always give false for null pointers

2017-11-13 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82869 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/82976] [8 Regression] Error: non-trivial conversion at assignment since r254526

2017-11-14 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82976 --- Comment #2 from Janne Blomqvist --- Hmm. I do think r254526 does the right thing (TM). Looking at -ftree-dump-original the frontend doesn't generaty any logical(kind=1) temporary variables. So presumably some optimization pass creates such a

[Bug fortran/82976] [8 Regression] Error: non-trivial conversion at assignment since r254526

2017-11-14 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82976 --- Comment #3 from Janne Blomqvist --- Yes, the logical(kind=4) definitely comes from the frontend. If you compile with -fdefault-integer-8 it changes to a logical(kind=8).

[Bug fortran/82976] [8 Regression] Error: non-trivial conversion at assignment since r254526

2017-11-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82976 --- Comment #5 from Janne Blomqvist --- So the problem is the logical(kind=1) one, it should be the same type as the LHS. It seems it originates from (from .003t.original): logical(kind=4) D.3603; ... D.3603 = (struct test_typ[0:] * restrict) c

[Bug fortran/82976] [8 Regression] Error: non-trivial conversion at assignment since r254526

2017-11-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82976 --- Comment #7 from Janne Blomqvist --- (In reply to Thomas Koenig from comment #6) > I cannot check at the moment, but I remember changing > the KIND of mask arguments generated by the compiler to kind=1, > to save memory. This is quite a few ye

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

2017-11-16 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829 --- Comment #32 from Janne Blomqvist --- Interestingly, Linux 4.14 contains a way to avoid a context switch to a threadpool in case the data is already in the page cache: https://kernelnewbies.org/Linux_4.14#head-8c8861fbded3e87631ab06bcd511f5f0d

[Bug fortran/44292] [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement

2017-11-17 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org

[Bug libfortran/83036] New: INQUIRE specifier NEXTREC is a 4-byte integer, should be 8

2017-11-17 Thread jb at gcc dot gnu.org
Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- When working on PR 44292, I happened to notice that the same issue affects the NEXTREC= specifier for the INQUIRE statement as well.

[Bug fortran/44292] [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement

2017-11-17 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 Janne Blomqvist changed: What|Removed |Added URL||https://gcc.gnu.org/ml/gcc-

[Bug libfortran/83036] INQUIRE specifier NEXTREC is a 4-byte integer, should be 8

2017-11-18 Thread jb at gcc dot gnu.org
- ||patches/2017-11/msg01624.ht ||ml Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org --- Comment #1 from Janne Blomqvist --- Patch: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01624

[Bug fortran/44292] [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 --- Comment #9 from Janne Blomqvist --- Author: jb Date: Sat Nov 18 16:13:20 2017 New Revision: 254915 URL: https://gcc.gnu.org/viewcvs?rev=254915&root=gcc&view=rev Log: PR 44292 Enable large record lengths in OPEN and INQUIRE statements This i

[Bug libfortran/83036] INQUIRE specifier NEXTREC is a 4-byte integer, should be 8

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83036 --- Comment #2 from Janne Blomqvist --- Author: jb Date: Sat Nov 18 16:56:21 2017 New Revision: 254916 URL: https://gcc.gnu.org/viewcvs?rev=254916&root=gcc&view=rev Log: PR 83036 Make NEXTREC specifier for INQUIRE work for large record numbers

[Bug libfortran/83036] INQUIRE specifier NEXTREC is a 4-byte integer, should be 8

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83036 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/44292] [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 Janne Blomqvist changed: What|Removed |Added URL|https://gcc.gnu.org/ml/gcc- |https://gcc.gnu.org/ml/gcc-

[Bug fortran/44292] [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 --- Comment #11 from Janne Blomqvist --- Author: jb Date: Sat Nov 18 22:05:13 2017 New Revision: 254918 URL: https://gcc.gnu.org/viewcvs?rev=254918&root=gcc&view=rev Log: PR 44292 Handle large record lengths Now that the ABI supports large reco

[Bug fortran/56818] [meta-bug] fortran-dev bugs

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56818 Bug 56818 depends on bug 44292, which changed state. Bug 44292 Summary: [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 What|Removed

[Bug fortran/44292] [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/29602] [F2003] I/O specifiers can now be of any kind

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29602 Bug 29602 depends on bug 44292, which changed state. Bug 44292 Summary: [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 What|Removed

[Bug fortran/53796] I/O INQUIRE of RECL: If not specified in OPEN, the default value should be returned (sequential access)

2017-11-18 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796 Bug 53796 depends on bug 44292, which changed state. Bug 44292 Summary: [libgfortran ABI breakage] Increase internal size of RECL= of the OPEN statement https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44292 What|Removed

[Bug libfortran/83070] New: -Wsign-compare warning in eoshift0

2017-11-20 Thread jb at gcc dot gnu.org
: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org Target Milestone: --- ../../../trunk-git/libgfortran/intrinsics/eoshift0.c: In function ‘eoshift0’: ../../../trunk-git/libgfortran/intrinsics/eoshift0.c:119:11: warning: comparison of integer

[Bug fortran/53796] I/O INQUIRE of RECL: If not specified in OPEN, the default value should be returned (sequential access)

2017-11-20 Thread jb at gcc dot gnu.org
- ||patches/2017-11/msg01807.ht ||ml Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org --- Comment #18 from Janne Blomqvist --- Patch: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01807

[Bug libfortran/83070] -Wsign-compare warning in eoshift0

2017-11-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83070 --- Comment #3 from Janne Blomqvist --- Author: jb Date: Wed Nov 22 08:51:21 2017 New Revision: 255045 URL: https://gcc.gnu.org/viewcvs?rev=255045&root=gcc&view=rev Log: PR 83070 Fix -Wsign-compare warning 2017-11-22 Janne Blomqvist

[Bug libfortran/83070] -Wsign-compare warning in eoshift0

2017-11-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83070 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 --- Comment #2 from Janne Blomqvist --- Author: jb Date: Wed Nov 22 19:19:13 2017 New Revision: 255072 URL: https://gcc.gnu.org/viewcvs?rev=255072&root=gcc&view=rev Log: PR 83097 Use __BYTE_ORDER__ predefined macro instead of runtime check By u

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #3

[Bug tree-optimization/40766] this fortran program is too slow

2017-11-23 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40766 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-23 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 --- Comment #4 from Janne Blomqvist --- Actually, I think it's for big endian we could optimize memcmp_char4. In the example Thomas posted on the mailing list, one must also check the sign of memcmp, not just whether it's != 0. Fixed example: #i

[Bug fortran/36313] [F03] {MIN,MAX}{LOC,VAL} should accept character arguments

2017-11-24 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36313 --- Comment #13 from Janne Blomqvist --- Author: jb Date: Fri Nov 24 08:51:15 2017 New Revision: 255135 URL: https://gcc.gnu.org/viewcvs?rev=255135&root=gcc&view=rev Log: PR 36313 Replace int with gfc_charlen_type, take 3 Still some prototypes

[Bug fortran/53796] I/O INQUIRE of RECL: If not specified in OPEN, the default value should be returned (sequential access)

2017-11-28 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796 --- Comment #19 from Janne Blomqvist --- Author: jb Date: Tue Nov 28 19:28:50 2017 New Revision: 255215 URL: https://gcc.gnu.org/viewcvs?rev=255215&root=gcc&view=rev Log: PR 53796 Improve INQUIRE(RECL=...) handling The current F2018 draft (N213

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

2016-08-31 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77261 Janne Blomqvist changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libfortran/77473] New PRNG causes regressions on DragonFly BSD

2016-10-01 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77473 --- Comment #2 from Janne Blomqvist --- (In reply to Rimvydas (RJ) from comment #0) > Created attachment 39550 [details] > changes to tests > > Native configuration is x86_64-unknown-dragonfly4.7 > > r239356 Replace KISS PRNG with xorshift1024*

[Bug libfortran/67585] Retry system calls failing with EINTR

2016-10-09 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67585 --- Comment #3 from Janne Blomqvist --- Author: jb Date: Sun Oct 9 18:05:56 2016 New Revision: 240902 URL: https://gcc.gnu.org/viewcvs?rev=240902&root=gcc&view=rev Log: PR 67585 Handle EINTR Many POSIX systems have the bad habit of not restart

[Bug libfortran/67585] Retry system calls failing with EINTR

2016-10-09 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67585 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

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

2016-10-09 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829 Janne Blomqvist changed: What|Removed |Added Status|ASSIGNED|NEW Assignee|jb at gcc dot

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #8 from Janne Blomqvist --- Author: jb Date: Sat Oct 15 13:14:15 2016 New Revision: 241199 URL: https://gcc.gnu.org/viewcvs?rev=241199&root=gcc&view=rev Log: PR 48587 Newunit allocator Currently GFortran newer reuses unit numbers al

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #9 from Janne Blomqvist --- Author: jb Date: Sat Oct 15 13:15:26 2016 New Revision: 241200 URL: https://gcc.gnu.org/viewcvs?rev=241200&root=gcc&view=rev Log: PR 48587 Newunit allocator 2016-10-15 Janne Blomqvist PR libfo

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #10 from Janne Blomqvist --- Author: jb Date: Sun Oct 16 06:28:15 2016 New Revision: 241211 URL: https://gcc.gnu.org/viewcvs?rev=241211&root=gcc&view=rev Log: PR 48587 Newunit allocator, cleanup Improve error message, and remove a r

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/51119] MATMUL slow for large matrices

2016-11-16 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #43 from Janne Blomqvist --- Compile warnings caused by this patch: cc1: warning: command line option ‘-fno-protect-parens’ is valid for Fortran but not for C cc1: warning: command line option ‘-fstack-arrays’ is valid for Fortran bu

[Bug fortran/60646] New: Investigate improved complex division algorithms

2014-03-25 Thread jb at gcc dot gnu.org
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org The paper http://arxiv.org/abs/1210.4539 analyzes several algorithms for complex division. Currently GFortran IIRC uses the Smith (1962) algorithm. We should investigate whether GFortran could

[Bug middle-end/60646] Investigate improved complex division algorithms

2014-03-28 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60646 Janne Blomqvist changed: What|Removed |Added Component|fortran |middle-end --- Comment #6 from Janne Bl

[Bug libfortran/60324] Handle arbitrarily long path names

2014-04-30 Thread jb at gcc dot gnu.org
||2014-04-30 Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Janne Blomqvist --- Assigning to myself, working on a patch.

[Bug libfortran/61035] New: Crash in getcwd intrinsic due to stack overflow

2014-05-02 Thread jb at gcc dot gnu.org
: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org The example program below crashes (my stack size limit is 8 MiB). program getcwd_overflow implicit none character(len=10485760) :: str ! 10 MiB call getcwd(str) print *, trim(str) end

[Bug libfortran/61035] Crash in getcwd intrinsic due to stack overflow

2014-05-02 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61035 Janne Blomqvist changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org

[Bug libfortran/61035] Crash in getcwd intrinsic due to stack overflow

2014-05-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61035 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED URL|

[Bug fortran/56919] [4.7/4.8 Regression] Wrong result for SYSTEM_CLOCK on Cygwin

2014-05-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56919 --- Comment #8 from Janne Blomqvist --- Author: jb Date: Sat May 3 20:56:26 2014 New Revision: 210041 URL: http://gcc.gnu.org/viewcvs?rev=210041&root=gcc&view=rev Log: PR 56919 Check _POSIX_MONOTONIC_CLOCK. 2014-05-03 Janne Blomqvist Ba

[Bug fortran/56919] [4.7/4.8 Regression] Wrong result for SYSTEM_CLOCK on Cygwin

2014-05-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56919 --- Comment #9 from Janne Blomqvist --- Author: jb Date: Sat May 3 21:03:10 2014 New Revision: 210042 URL: http://gcc.gnu.org/viewcvs?rev=210042&root=gcc&view=rev Log: PR 56919 Check _POSIX_MONOTONIC_CLOCK. 2014-05-04 Janne Blomqvist Ba

[Bug fortran/56919] [4.7/4.8 Regression] Wrong result for SYSTEM_CLOCK on Cygwin

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

[Bug libfortran/61035] Crash in getcwd intrinsic due to stack overflow

2014-05-12 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61035 --- Comment #3 from Janne Blomqvist --- Author: jb Date: Mon May 12 19:23:11 2014 New Revision: 210335 URL: http://gcc.gnu.org/viewcvs?rev=210335&root=gcc&view=rev Log: Fix stack overflow crash in getcwd intrinsic. 2014-05-12 Janne Blomqvist

[Bug libfortran/61035] Crash in getcwd intrinsic due to stack overflow

2014-05-12 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61035 Janne Blomqvist changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libfortran/61187] New: valgrind errors if stdin is closed

2014-05-14 Thread jb at gcc dot gnu.org
Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org In some cases STDIN_FILENO (0 in POSIX) can be closed. This happens e.g. for rank != 0 MPI processes with MPICH2. This results in valgrind complaining about uninitialized variables. Test program

[Bug libfortran/61187] valgrind errors if stdin is closed

2014-05-16 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61187 --- Comment #1 from Janne Blomqvist --- Author: jb Date: Fri May 16 20:37:13 2014 New Revision: 210527 URL: http://gcc.gnu.org/viewcvs?rev=210527&root=gcc&view=rev Log: PR 61187 Fix use of uninitialized memory. 2014-05-16 Janne Blomqvist

[Bug libfortran/61187] valgrind errors if stdin is closed

2014-05-16 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61187 --- Comment #2 from Janne Blomqvist --- Author: jb Date: Fri May 16 20:42:56 2014 New Revision: 210529 URL: http://gcc.gnu.org/viewcvs?rev=210529&root=gcc&view=rev Log: PR 61187 Fix use of uninitialized data. 2014-05-16 Janne Blomqvist

[Bug libfortran/61187] valgrind errors if stdin is closed

2014-05-16 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61187 --- Comment #3 from Janne Blomqvist --- Author: jb Date: Fri May 16 20:48:17 2014 New Revision: 210530 URL: http://gcc.gnu.org/viewcvs?rev=210530&root=gcc&view=rev Log: PR 61187 Fix use of uninitialized data. 2014-05-16 Janne Blomqvist

[Bug libfortran/60324] Handle arbitrarily long path names

2014-05-21 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60324 --- Comment #2 from Janne Blomqvist --- Author: jb Date: Thu May 22 03:51:25 2014 New Revision: 210738 URL: http://gcc.gnu.org/viewcvs?rev=210738&root=gcc&view=rev Log: PR 60324 Handle long path names, don't use PATH_MAX. Modified: trunk/li

[Bug libfortran/60324] Handle arbitrarily long path names

2014-05-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60324 --- Comment #3 from Janne Blomqvist --- Author: jb Date: Thu May 22 21:17:29 2014 New Revision: 210827 URL: http://gcc.gnu.org/viewcvs?rev=210827&root=gcc&view=rev Log: PR 60324 Handle long path names, don't use PATH_MAX. 2014-05-23 Janne Blom

[Bug libfortran/61187] valgrind errors if stdin is closed

2014-05-25 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61187 --- Comment #5 from Janne Blomqvist --- Author: jb Date: Sun May 25 19:29:00 2014 New Revision: 210914 URL: http://gcc.gnu.org/viewcvs?rev=210914&root=gcc&view=rev Log: PR 61187 Avoid reading uninitialized memory. 2014-05-25 Janne Blomqvist

[Bug libfortran/61187] valgrind errors if stdin is closed

2014-05-25 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61187 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/61310] New: Regression, CTIME intrinsic incorrect result string

2014-05-25 Thread jb at gcc dot gnu.org
Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: jb at gcc dot gnu.org As a result of PR 47432, the CTIME intrinsic was changed to use the ctime_r() function if available instead of the C stdlib ctime(). However, due to some problems that was changed to use

[Bug libfortran/61310] Regression, CTIME intrinsic incorrect result string

2014-05-25 Thread jb at gcc dot gnu.org
- ||patches/2014-05/msg02124.ht ||ml Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org --- Comment #1 from Janne Blomqvist --- Patch at https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02124

[Bug libfortran/61310] Regression, CTIME intrinsic incorrect result string

2014-05-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61310 --- Comment #2 from Janne Blomqvist --- Author: jb Date: Mon May 26 18:17:13 2014 New Revision: 210938 URL: http://gcc.gnu.org/viewcvs?rev=210938&root=gcc&view=rev Log: PR 61310 Rewrite implementation of CTIME and FDATE intrinsics. 2014-05-26

[Bug libfortran/61310] Regression, CTIME intrinsic incorrect result string

2014-05-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61310 --- Comment #3 from Janne Blomqvist --- Author: jb Date: Mon May 26 18:28:49 2014 New Revision: 210941 URL: http://gcc.gnu.org/viewcvs?rev=210941&root=gcc&view=rev Log: PR 61310 Rewrite implementation of CTIME and FDATE intrinsics. 2014-05-26

[Bug libfortran/61310] Regression, CTIME intrinsic incorrect result string

2014-05-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61310 --- Comment #4 from Janne Blomqvist --- Author: jb Date: Mon May 26 18:36:01 2014 New Revision: 210943 URL: http://gcc.gnu.org/viewcvs?rev=210943&root=gcc&view=rev Log: PR 61310 Rewrite implementation of CTIME and FDATE intrinsics. 2014-05-26

[Bug libfortran/61310] Regression, CTIME intrinsic incorrect result string

2014-05-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61310 --- Comment #5 from Janne Blomqvist --- Author: jb Date: Mon May 26 19:44:24 2014 New Revision: 210947 URL: http://gcc.gnu.org/viewcvs?rev=210947&root=gcc&view=rev Log: PR 61310 Rewrite implementation of CTIME and FDATE intrinsics. 2014-05-26

[Bug libfortran/61310] Regression, CTIME intrinsic incorrect result string

2014-05-26 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61310 Janne Blomqvist changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/56981] Slow I/O: Unformatted 5x slower, large sys component; formatted slow as well

2014-06-07 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56981 --- Comment #10 from Janne Blomqvist --- Author: jb Date: Sun Jun 8 05:43:29 2014 New Revision: 211353 URL: http://gcc.gnu.org/viewcvs?rev=211353&root=gcc&view=rev Log: PR 56981 Flush buffer at record boundary if possible. 2014-06-08 Janne Bl

[Bug libfortran/60324] Handle arbitrarily long path names

2014-06-10 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60324 Janne Blomqvist changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

<    1   2   3   4   5   6   7   >