http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51803
--- Comment #5 from Janne Blomqvist 2012-01-11 07:34:22
UTC ---
Author: jb
Date: Wed Jan 11 07:34:16 2012
New Revision: 183090
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183090
Log:
PR 51803 Handle getcwd failure and lack of the funct
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51803
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51820
Bug #: 51820
Summary: [doc] underscoring documentation incorrect
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Prior
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51803
--- Comment #7 from Janne Blomqvist 2012-01-12 09:58:39
UTC ---
Author: jb
Date: Thu Jan 12 09:58:34 2012
New Revision: 183122
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183122
Log:
PR 51803 Avoid malloc if getcwd fails or is not avai
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51842
Janne Blomqvist changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51842
--- Comment #5 from Janne Blomqvist 2012-01-13 10:19:02
UTC ---
(In reply to comment #3)
> (In reply to comment #0)
> > /* The type used of array indices, amongst other things. */
> > typedef ssize_t index_type;
>
> I just saw that GCC 4.7 uses
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51842
--- Comment #7 from Janne Blomqvist 2012-01-13 11:44:05
UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > Yes, and no. It is perhaps a better match for the current frontend logic of
> > choosing a type equal to the pointer size, but
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51842
Janne Blomqvist changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
||http://gcc.gnu.org/ml/gcc-p
||atches/2012-01/msg00715.htm
||l
Last reconfirmed||2012-01-13
AssignedTo|unassigned at gcc dot |jb at gcc dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51808
--- Comment #2 from Janne Blomqvist 2012-01-29 17:19:38
UTC ---
Author: jb
Date: Sun Jan 29 17:19:32 2012
New Revision: 183677
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183677
Log:
PR 51808 Support arbitrarily long bind(C) binding la
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51808
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51808
--- Comment #4 from Janne Blomqvist 2012-01-29 17:41:54
UTC ---
Author: jb
Date: Sun Jan 29 17:41:49 2012
New Revision: 183678
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183678
Log:
PR 51808 Fix ChangeLog entry
Modified:
trunk/gc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51808
--- Comment #5 from Janne Blomqvist 2012-01-29 19:01:14
UTC ---
Author: jb
Date: Sun Jan 29 19:01:09 2012
New Revision: 183679
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183679
Log:
PR 51808 Constify binding_label.
2012-01-29 Janne
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
When building libgfortran trunk one nowadays (within the past month or two,
maybe?) gets lots of warnings like below:
In file included from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796
--- Comment #23 from Janne Blomqvist ---
Author: jb
Date: Wed Aug 7 07:34:10 2019
New Revision: 274160
URL: https://gcc.gnu.org/viewcvs?rev=274160&root=gcc&view=rev
Log:
PR 53796 Make inquire(file=, recl=) conform to F2018
In my original patch
: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
As of Fortran 2018, procedures are recursive by default. However, currently
GFortran places automatic
: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Currently GFortran uses the xorshift1024* PRNG. The author of that PRNG has an
improved PRNG "xoshiro" at http://prng.di.unimi.it/ , described in detail at
https://arxiv.org/abs/1805.01407 . GFor
-
||patches/2019-08/msg00679.ht
||ml
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
--- Comment #2 from Janne Blomqvist ---
Patch at https://gcc.gnu.org/ml/gcc-patches/2019-08/msg00679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
Janne Blomqvist changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
Janne Blomqvist changed:
What|Removed |Added
URL||https://gcc.gnu.org/ml/gcc-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91413
--- Comment #3 from Janne Blomqvist ---
Author: jb
Date: Sun Aug 11 09:42:41 2019
New Revision: 274264
URL: https://gcc.gnu.org/viewcvs?rev=274264&root=gcc&view=rev
Log:
PR fortran/91413 Generate warning when making array static
When moving a l
||2019-08-12
CC||jb at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Janne Blomqvist ---
AFAICT this is a valid bug report, albeit maybe not of the highest priority.
The problem is that the code in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
--- Comment #4 from Janne Blomqvist ---
Author: jb
Date: Tue Aug 13 08:24:43 2019
New Revision: 274361
URL: https://gcc.gnu.org/viewcvs?rev=274361&root=gcc&view=rev
Log:
PR fortran/91414: Improved PRNG
Update the PRNG from xorshift1024* to xosh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
--- Comment #5 from Janne Blomqvist ---
Author: jb
Date: Tue Aug 13 08:42:43 2019
New Revision: 274362
URL: https://gcc.gnu.org/viewcvs?rev=274362&root=gcc&view=rev
Log:
PR fortran/91414 Improve initialization of PRNG
As part of PR 91414 an imp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
--- Comment #6 from Janne Blomqvist ---
Author: jb
Date: Tue Aug 13 09:00:46 2019
New Revision: 274363
URL: https://gcc.gnu.org/viewcvs?rev=274363&root=gcc&view=rev
Log:
PR fortran/91414 Improve initialization of PRNG
As part of PR 91414 an imp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
--- Comment #7 from Janne Blomqvist ---
Author: jb
Date: Tue Aug 13 09:02:25 2019
New Revision: 274364
URL: https://gcc.gnu.org/viewcvs?rev=274364&root=gcc&view=rev
Log:
PR fortran/91414 Correctly fill master_state from os_seed.
Modified:
b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
--- Comment #8 from Janne Blomqvist ---
Author: jb
Date: Tue Aug 13 09:04:18 2019
New Revision: 274365
URL: https://gcc.gnu.org/viewcvs?rev=274365&root=gcc&view=rev
Log:
PR fortran/91414 Bugfix for previous commit
Correctly fill master_seed fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91414
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
||jb at gcc dot gnu.org
Blocks||91300
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
--- Comment #11 from Janne Blomqvist ---
The variadic os_error type function is probably also necessary for solving PR
91300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68401
Janne Blomqvist changed:
What|Removed |Added
URL||https://gcc.gnu.org/ml/gcc-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68401
--- Comment #13 from Janne Blomqvist ---
Author: jb
Date: Sat Aug 17 05:45:37 2019
New Revision: 274599
URL: https://gcc.gnu.org/viewcvs?rev=274599&root=gcc&view=rev
Log:
PR fortran/68401 Improve allocation error message
Improve the error messa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91300
Bug 91300 depends on bug 68401, which changed state.
Bug 68401 Summary: improve 'Allocation would exceed memory limit'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68401
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68401
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91443
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91413
Janne Blomqvist changed:
What|Removed |Added
Assignee|jb at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48419
--- Comment #9 from Janne Blomqvist ---
Like Jerry said, we've recently had an ABI break (two, actually!), and I think
we should try hard to avoid yet another one. I think it should be possible to
create some new st_parameter_dt_2 or such, as we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91543
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796
Janne Blomqvist changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Consider the testcase
subroutine foo()
implicit none
character(len=4) :: s
s = "a"
associate(w => trim(s))
end associate
end subroutine f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
Janne Blomqvist changed:
What|Removed |Added
Depends on||83344
--- Comment #19 from Janne Blomq
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83344
--- Comment #2 from Janne Blomqvist ---
Seems it's wrong at least to access value.character.length if the expression
isn't a constant? So,
diff --git a/gcc/fortran/resolve.c b/gcc/fortran/resolve.c
index d1a2368..017b9f7 100644
--- a/gcc/fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83344
--- Comment #9 from Janne Blomqvist ---
With the patch in #2 (which in this case is equivalent to your patch in #8) I
get on my charlen->size_t branch:
❯ gfortran -O0 -Wall -c a22.f90
a22.f90:20:0:
associate(w4 => trim(s))
Warning: ‘.w4’ is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83344
--- Comment #10 from Janne Blomqvist ---
Author: jb
Date: Thu Dec 28 18:49:12 2017
New Revision: 256021
URL: https://gcc.gnu.org/viewcvs?rev=256021&root=gcc&view=rev
Log:
PR fortran/83344 Don't set bogus constant value
This patch does not fix P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83567
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #4
: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Consider the testcase
program largewr
integer(kind=1) :: a(2_8**31+1)
a = 0
a(size(a, kind=8)) = 1
open(10, file="largewr.dat", access="stream", form="unformatted&qu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83649
--- Comment #1 from Janne Blomqvist ---
I forgot a reference; see http://man7.org/linux/man-pages/man2/read.2.html
https://stackoverflow.com/questions/38586144/error-when-trying-to-write-a-file-larger-than-2-gb-on-linux
suggests that macOS isn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83649
--- Comment #2 from Janne Blomqvist ---
Author: jb
Date: Tue Jan 2 13:25:10 2018
New Revision: 256074
URL: https://gcc.gnu.org/viewcvs?rev=256074&root=gcc&view=rev
Log:
PR libgfortran/83649 Chunk large reads and writes
It turns out that Linux
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83649
Janne Blomqvist changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83649
--- Comment #6 from Janne Blomqvist ---
Author: jb
Date: Wed Jan 3 11:46:38 2018
New Revision: 256172
URL: https://gcc.gnu.org/viewcvs?rev=256172&root=gcc&view=rev
Log:
PR libgfortran/83649 Chunk large reads and writes
Backport from trunk.
It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83649
--- Comment #7 from Janne Blomqvist ---
Author: jb
Date: Wed Jan 3 12:08:05 2018
New Revision: 256173
URL: https://gcc.gnu.org/viewcvs?rev=256173&root=gcc&view=rev
Log:
PR libgfortran/83649 Chunk large reads and writes
Backport from trunk.
It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83649
Janne Blomqvist changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310
--- Comment #17 from Janne Blomqvist ---
Author: jb
Date: Fri Jan 5 19:01:12 2018
New Revision: 256284
URL: https://gcc.gnu.org/viewcvs?rev=256284&root=gcc&view=rev
Log:
PR 78534 Change character length from int to size_t
In order to handle la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #20 from Janne Blomqvist ---
Author: jb
Date: Fri Jan 5 19:01:12 2018
New Revision: 256284
URL: https://gcc.gnu.org/viewcvs?rev=256284&root=gcc&view=rev
Log:
PR 78534 Change character length from int to size_t
In order to handle la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50892
--- Comment #9 from Janne Blomqvist ---
Following r256284 (PR 78534) the original testcase ICE's. Interestingly, the
reduced testcases in #c2 and #c3 work fine.
The patch below fixes the ICE
diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50892
--- Comment #10 from Janne Blomqvist ---
Author: jb
Date: Sat Jan 6 10:41:03 2018
New Revision: 256310
URL: https://gcc.gnu.org/viewcvs?rev=256310&root=gcc&view=rev
Log:
PR 50892 Latent bug in char pointer assignment
Due to r256284 (PR 78534)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #22 from Janne Blomqvist ---
Author: jb
Date: Sat Jan 6 10:42:57 2018
New Revision: 256311
URL: https://gcc.gnu.org/viewcvs?rev=256311&root=gcc&view=rev
Log:
PR 78534 libgfortran ChangeLog
The libgfortran/ChangeLog entry was accide
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
--- Comment #1 from Janne Blomqvist ---
> which makes sense for variables, but IMO not for parameters.
I agree, that's why a few lines before that block checking the size limit we
have:
/* For further simplification, we need the character st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
--- Comment #2 from Janne Blomqvist ---
With the following patch the testcase works:
diff --git a/gcc/fortran/simplify.c b/gcc/fortran/simplify.c
index 3e5abd4..d68975c 100644
--- a/gcc/fortran/simplify.c
+++ b/gcc/fortran/simplify.c
@@ -6084,8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #3 from Janne Blomqvist ---
If I compile with -O2, or compile with -O0 and set the stack size limit to
unlimited before running, the segfault disappears for me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #8 from Janne Blomqvist ---
Good catch! Though as is, there's a few warnings due to signed/unsigned
comparisons. Some minor fixes results in:
diff --git a/libgfortran/io/write.c b/libgfortran/io/write.c
index 3aa2f0e..f966917 100644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #10 from Janne Blomqvist ---
Author: jb
Date: Sat Jan 6 19:09:52 2018
New Revision: 256313
URL: https://gcc.gnu.org/viewcvs?rev=256313&root=gcc&view=rev
Log:
PR 83704 Use size_t in write_character
For printing long characters, we n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #23 from Janne Blomqvist ---
Author: jb
Date: Sun Jan 7 10:17:52 2018
New Revision: 256322
URL: https://gcc.gnu.org/viewcvs?rev=256322&root=gcc&view=rev
Log:
PR 78534, 83704 Handle large formatted I/O
In order to handle large chara
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #11 from Janne Blomqvist ---
Author: jb
Date: Sun Jan 7 10:17:52 2018
New Revision: 256322
URL: https://gcc.gnu.org/viewcvs?rev=256322&root=gcc&view=rev
Log:
PR 78534, 83704 Handle large formatted I/O
In order to handle large chara
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #12 from Janne Blomqvist ---
With these two commits in #c10 and #c11 the testcase now works correctly.
However, if one enables warnings there's still the (spurious) warning:
test1.f90:12:18:
ch = '123456789'
1
W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83725
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #2 from Janne Blom
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83725
--- Comment #6 from Janne Blomqvist ---
Hmm, the attached testcase works just fine for me. No ICE observed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #17 from Janne Blomqvist ---
I have fixed resolve_ordinary_assign as part of a larger patch fixing similar
issues in the frontend (you also need to change extract_int to extract_hwi). I
can submit it once I have tackled the 32-bit reg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #24 from Janne Blomqvist ---
Author: jb
Date: Mon Jan 8 12:12:05 2018
New Revision: 256337
URL: https://gcc.gnu.org/viewcvs?rev=256337&root=gcc&view=rev
Log:
PR 78534 Regression on 32-bit targets
By switching from int to size_t in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83740
Janne Blomqvist changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83740
--- Comment #5 from Janne Blomqvist ---
Author: jb
Date: Wed Jan 10 11:34:45 2018
New Revision: 256426
URL: https://gcc.gnu.org/viewcvs?rev=256426&root=gcc&view=rev
Log:
PR 83740 Wrong string length type in bounds check
This patch fixes up the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83740
--- Comment #6 from Janne Blomqvist ---
Should be fixed by r256425 (and r256426). Gerhard, can you verify whether the
ICE you reported also goes away, given that neither me nor Jakub in #c3 were
able to reproduce it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29651
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83740
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #18 from Janne Blomqvist ---
Author: jb
Date: Mon Jan 22 13:31:08 2018
New Revision: 256944
URL: https://gcc.gnu.org/viewcvs?rev=256944&root=gcc&view=rev
Log:
PR 78534, 83704 Large character lengths
This patch fixes various parts of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #25 from Janne Blomqvist ---
Author: jb
Date: Mon Jan 22 13:31:08 2018
New Revision: 256944
URL: https://gcc.gnu.org/viewcvs?rev=256944&root=gcc&view=rev
Log:
PR 78534, 83704 Large character lengths
This patch fixes various parts of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
Janne Blomqvist changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |WAITING
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
--- Comment #26 from Janne Blomqvist ---
Author: jb
Date: Wed Jan 31 13:23:20 2018
New Revision: 257233
URL: https://gcc.gnu.org/viewcvs?rev=257233&root=gcc&view=rev
Log:
PR 78534 Reinstate better string copy algorithm
As part of the change to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
--- Comment #8 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 1 07:41:03 2018
New Revision: 257281
URL: https://gcc.gnu.org/viewcvs?rev=257281&root=gcc&view=rev
Log:
PR 83705 Repeat with large values
This patch fixes the regression by incre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
--- Comment #8 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 1 19:47:15 2018
New Revision: 257310
URL: https://gcc.gnu.org/viewcvs?rev=257310&root=gcc&view=rev
Log:
PR 83975 Associate target with non-constant character length
When associat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83344
--- Comment #11 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 1 19:47:15 2018
New Revision: 257310
URL: https://gcc.gnu.org/viewcvs?rev=257310&root=gcc&view=rev
Log:
PR 83975 Associate target with non-constant character length
When associa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81552
--- Comment #5 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 14 21:33:29 2019
New Revision: 268906
URL: https://gcc.gnu.org/viewcvs?rev=268906&root=gcc&view=rev
Log:
PR 81552 Improve and document -flag-init-integer
Make the option handling
||jb at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #6 from Janne Blomqvist ---
Fixed on trunk, closing.
The patch uses strtol() since that is in C89 and thus available everywhere.
This close to the GCC 9 release I didn't want to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89274
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82480
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #3
||jb at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #3 from Janne Blomqvist ---
Indeed, this is invalid, as the GFortran I/O library is anything by
async-signal-safe.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77908
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80408
--- Comment #5 from Janne Blomqvist ---
(In reply to Raphael Monod from comment #4)
> Thank you for your answer. But I don't understand why adding -lpthread
> option change the behavior if I do not use any thread.
In libgfortran, if a thread lib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84509
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32770
Bug 32770 depends on bug 84509, which changed state.
Bug 84509 Summary: STOP and ERROR STOP statements with -fdefault-integer-8 and
large stop code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84509
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52879
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jb at gcc dot gnu.org
Target Milestone: ---
Occasionally there are problems like
https://stackoverflow.com/questions/55120720/fortran-execute-command-line-runtime-error-depends-on-memory-consumption
where
||jb at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #1 from Janne Blomqvist ---
It's not a thread-safety issue. If you uncomment the line
close(lun)
you get the same error message also without OpenMP. The reason is that
GFo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
Janne Blomqvist changed:
What|Removed |Added
CC||jb at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329
--- Comment #5 from Janne Blomqvist ---
(In reply to Thomas Koenig from comment #4)
> (In reply to Janne Blomqvist from comment #3)
> > 1) When compiling an external procedure, for character(len=1) arguments we
> > don't generate the hidden strin
201 - 300 of 690 matches
Mail list logo
