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=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=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=83704
--- Comment #16 from Thomas Koenig ---
I hadn't actually compiled this... but then this at least compiles.
Index: resolve.c
===
--- resolve.c (Revision 256284)
+++ resolve.c (Ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #15 from Dominique d'Humieres ---
> does this help?
Nope, I get
../../work/gcc/fortran/resolve.c: In function 'bool
resolve_ordinary_assign(gfc_code*, gfc_namespace*)':
../../work/gcc/fortran/resolve.c:10281:27: error: format '%d' e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
Thomas Koenig changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #13 from Dominique d'Humieres ---
> Which looks like a clear case of integer wraparound. Given that
> the testcase works, apparently correctly, I would guess the it's
> an error in the implementation of the -Wcharacter-truncation warn
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=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 #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=83704
--- Comment #9 from Jerry DeLisle ---
(In reply to Janne Blomqvist from comment #8)
> - for (i = 0; i < length; i++)
> + for (size_t = 0; i < length; i++)
typo above. Change to:
+ for (size_t i = 0; i < length; i++)
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 #7 from Jerry DeLisle ---
(In reply to Dominique d'Humieres from comment #6)
> > However this does not fix the output of
>
> print *, "'", ch(1:2_8**32_8+3_8), "'"
>
> This is fixed by the following patch
>
> --- ../_clean/libgfo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #6 from Dominique d'Humieres ---
> However this does not fix the output of
print *, "'", ch(1:2_8**32_8+3_8), "'"
This is fixed by the following patch
--- ../_clean/libgfortran/io/write.c2018-01-05 20:02:38.0 +0100
++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #5 from Dominique d'Humieres ---
> If I compile with -O2, or compile with -O0 and set the stack size limit
> to unlimited before running, the segfault disappears for me.
I can confirmed that the 'Illegal instruction' is gone if I com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
--- Comment #4 from Jerry DeLisle ---
I can compile it fine, but do not have enough memory to run it. So dominiq, how
much RAM do you have, maybe I can find a machine of sufficient capacity. One
has to be careful we dont take someones OS to its k
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 #2 from Dominique d'Humieres ---
> Is this with or without Janne's library side patch?
with or without.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704
Dominique d'Humieres changed:
What|Removed |Added
Keywords||wrong-code
Status|UNC
20 matches
Mail list logo
