https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #9 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:f7c2be50afa7935d3a05e3c7761e69d8b539da5b
commit r10-9001-gf7c2be50afa7935d3a05e3c7761e69d8b539da5b
Author: Jakub Jelinek
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:81372618277bfae682434fcdc80b311ee6007476
commit r11-4902-g81372618277bfae682434fcdc80b311ee6007476
Author: Jakub Jelinek
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #7 from Jakub Jelinek ---
Created attachment 49529
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49529&action=edit
gcc11-pr97768.patch
More complete (but still untested) patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #6 from Jakub Jelinek ---
I'd have thought doing it inside of
if (ex->ts.u.cl && ex->ts.u.cl->length)
conditional and testing for ex->ts.u.cl->length->expr_type instead.
Plus for the CHARACTER case, it doesn't need to use buffer and c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #4 from Jakub Jelinek ---
Or the length could be e.g. local variable:
subroutine baz (lens)
use fortran_strings, only : to_upper, operator(.in.)
integer :: lens
character(len=lens) str
logical l
str = ''
l = 32 .in. to_upp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
Jakub Jelinek changed:
What|Removed |Added
CC||markeggleston at gcc dot
gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #2 from Jakub Jelinek ---
If in the testcase I change the penultimate line to:
l = 32 .in. to_upper(str)
so that an error is emitted, the 64-bit little-endian f951 emits:
Error: Operands of user operator ‘in’ at (1) are INTEGER(4)/C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
--- Comment #1 from Jakub Jelinek ---
Seems this is only in the pretty-printing for message that would be printed if
there was an error later on (which there is not).
So I guess it really doesn't matter that much what exactly it prints, but it
sh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97768
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |10.3
11 matches
Mail list logo
