[Bug fortran/89077] ICE using * as len specifier for character parameter

2019-01-28 Thread rrodrigues at poli dot ufrj.br
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89077 --- Comment #3 from Rodrigo Rodrigues --- I'm not sure it is related, but in this test case, I don't get internal errors, but wrong results: program reverse implicit none character(20), parameter :: input = 'Forward' integer i character(

[Bug fortran/89077] ICE using * as len specifier for character parameter

2019-01-27 Thread rrodrigues at poli dot ufrj.br
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89077 --- Comment #1 from Rodrigo Rodrigues --- Moreover, removing the parameter specifier also produces an ICE: character(len(str)) :: str2 = transfer([(str(i:i), i=1,len(str))], str) > internal compiler error: in gfc_conv_string_init, at fortran/

[Bug fortran/89077] New: ICE using * as len specifier for character parameter

2019-01-27 Thread rrodrigues at poli dot ufrj.br
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: rrodrigues at poli dot ufrj.br Target Milestone: --- I am getting an Internal Compiler Error when I use assumed character length (*) in a parameter declaration, when using character substring (apparently, compiler

[Bug fortran/58913] Segmentation fault on real128 array

2013-11-24 Thread rrodrigues at poli dot ufrj.br
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 Rodrigo Rodrigues changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/58913] Segmentation fault on real128 array

2013-11-12 Thread rrodrigues at poli dot ufrj.br
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 --- Comment #10 from Rodrigo Rodrigues --- (In reply to Steve Kargl from comment #8) > On Tue, Oct 29, 2013 at 08:39:15PM +0000, rrodrigues at poli dot ufrj.br > wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 > >

[Bug fortran/58913] Segmentation fault on real128 array

2013-10-29 Thread rrodrigues at poli dot ufrj.br
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 --- Comment #9 from Rodrigo Rodrigues --- (In reply to Steve Kargl from comment #8) > Unfortnately, your trace suggests to me that this is MingW > specific. I can't help beyond this point. Prehaps, ping > the MingW developers? Yeah, I have to

[Bug fortran/58913] Segmentation fault on real128 array

2013-10-29 Thread rrodrigues at poli dot ufrj.br
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 --- Comment #7 from Rodrigo Rodrigues --- Here goes the backtrack: #0 0x in ?? () #1 0x0042d483 in output_float_FMT_G_16 (comp_d=, zero_flag=, sign_bit=, size=, buffer=, m=, f=0x22fb6c, dtp=) at ../../../gcc-4.8.0-min

[Bug fortran/58913] Segmentation fault on real128 array

2013-10-29 Thread rrodrigues at poli dot ufrj.br
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 --- Comment #5 from Rodrigo Rodrigues --- There is no compile error. Adding -g for running doesn't show any new information, just the same: Program received signal SIGSEGV: Segmentation Fault - invalid memory reference. Backtrace for this error:

[Bug fortran/58913] Segmentation fault on real128 array

2013-10-29 Thread rrodrigues at poli dot ufrj.br
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58913 --- Comment #3 from Rodrigo Rodrigues --- Windows 7 x86 I got gfortran from mingw. Actually, real128 returns 16 in my machine. It is totally equivalent to 16 here.

[Bug fortran/58913] New: Segmentation fault on real128 array

2013-10-29 Thread rrodrigues at poli dot ufrj.br
Assignee: unassigned at gcc dot gnu.org Reporter: rrodrigues at poli dot ufrj.br I cannot "write" a variable which contains an array of real(kind=real128). Scalars seem to work right. I got this behavior when running this simple program: 01 program main 02use iso_fort