PGI User Forum
 SearchSearch   MemberlistMemberlist     RegisterRegister   ProfileProfile    Log inLog in 

Free OpenACC Webinar

Dynamic type information lost? (PGI 13.7)
Goto page Previous  1, 2
 
Post new topic   Reply to topic    PGI User Forum Forum Index -> Programming and Compiling
View previous topic :: View next topic  
Author Message
jtull



Joined: 30 Jun 2004
Posts: 445

PostPosted: Fri Jan 24, 2014 2:53 pm    Post subject: TPR 19613 - empty derived types shouldnot be flagged as errs Reply with quote

This problem is fixed in the 14.1 release.

thanks,
dave
Back to top
View user's profile
Sean Patrick Santos



Joined: 15 Sep 2013
Posts: 15

PostPosted: Wed Apr 09, 2014 7:48 pm    Post subject: Reply with quote

Original case seems OK, but I found one case where an empty type can still cause a segfault in PGI 14.1.

Code:

program test_select_type_component

type :: foo
end type foo

type(foo) :: test_foo

! Produces an ICE.
allocate(test_foo, source=foo())

end program test_select_type_component
Back to top
View user's profile
cparrott



Joined: 02 May 2011
Posts: 146

PostPosted: Thu Apr 10, 2014 10:09 am    Post subject: Reply with quote

Hi Sean,

I note that the segfault is still present in 14.3, although it does also print out an error message:

Code:

cparrott@galaxy ~/UF $ pgf90 -o test_select test_select.f90
PGF90-S-0198-Illegal use of test_foo in ALLOCATE/DEALLOCATE (test_select.f90: 9)
pgf90-Fatal-/proj/pgi/linux86-64/14.3/bin/pgf901 TERMINATED by signal 11
Arguments to /proj/pgi/linux86-64/14.3/bin/pgf901
/proj/pgi/linux86-64/14.3/bin/pgf901 test_select.f90 -opt 1 -terse 1 -inform warn -nohpf -nostatic -x 19 0x400000 -quad -x 59 4 -x 15 2 -x 49 0x400004 -x 51 0x20 -x 57 0x4c -x 58 0x10000 -x 124 0x1000 -tp sandybridge -x 57 0xfb0000 -x 58 0x78031040 -x 48 4608 -x 49 0x100 -x 120 0x200 -stdinc /proj/pgi/linux86-64/14.3/include-gcc44:/proj/pgi/linux86-64/14.3/include:/usr/local/include:/usr/lib/gcc/x86_64-redhat-linux/4.4.6/include:/usr/include -def unix -def __unix -def __unix__ -def linux -def __linux -def __linux__ -def __NO_MATH_INLINES -def __x86_64 -def __x86_64__ -def __LONG_MAX__=9223372036854775807L -def '__SIZE_TYPE__=unsigned long int' -def '__PTRDIFF_TYPE__=long int' -def __THROW= -def __extension__= -def __amd_64__amd64__ -def __k8 -def __k8__ -def __SSE__ -def __MMX__ -def __SSE2__ -def __SSE3__ -def __SSSE3__ -freeform -vect 48 -y 54 1 -x 70 0x40000000 -modexport /tmp/pgf90C9zhuSjjUpSJ.cmod -modindex /tmp/pgf9089zh0oxWdN09.cmdx -output /tmp/pgf9089zh0957Lndt.ilm


Still, the compiler probably shouldn't crash in this case. I'll file a report.

Best regards,

+chris
Back to top
View user's profile
Sean Patrick Santos



Joined: 15 Sep 2013
Posts: 15

PostPosted: Thu Apr 10, 2014 11:04 am    Post subject: Reply with quote

Oops. I meant to post this valid code (which has the same issue):

Code:

program test_select_type_component

type :: foo
end type foo

type(foo), allocatable :: test_foo

! Produces an ICE.
allocate(test_foo, source=foo())

end program test_select_type_component
Back to top
View user's profile
jtull



Joined: 30 Jun 2004
Posts: 445

PostPosted: Mon Jun 16, 2014 5:28 pm    Post subject: TPR 20200 has been fixed in the 14.6 release Reply with quote

TPR 20200 - "Improper ALLOCATE statement triggers segfault in compiler"
has been fixed in the current 14.6 release.

thanks,
dave
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    PGI User Forum Forum Index -> Programming and Compiling All times are GMT - 7 Hours
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © phpBB Group