binary size changed while switching from pgi-6.1 to pgi-6.2

Since I have switched from pgi-6.1 to pgi-6.2, the size of the programs that are generated with pgcc has increased by a factor 3 to 10.
Here is a simple example :

[15:54:19]arthur@tantal238:~/tantale/src/test$ cat hello.c
#include <stdio.h>

int main (int argc, char *argv[]) {
    printf ("Hello world !\n");
    return 0;
}
[15:54:23]arthur@tantal238:~/tantale/src/test$ pgcc -V
pgcc 6.1-3 64-bit target on x86-64 Linux
Copyright 1989-2000, The Portland Group, Inc.  All Rights Reserved.
Copyright 2000-2006, STMicroelectronics, Inc.  All Rights Reserved.
[15:54:46]arthur@tantal238:~/tantale/src/test$ pgcc -o hello-6.1 hello.c
[15:55:02]arthur@tantal238:~/tantale/src/test$ module unload pgi/6.1
[15:56:36]arthur@tantal238:~/tantale/src/test$ module load pgi/6.2
[15:56:42]arthur@tantal238:~/tantale/src/test$ pgcc -V
pgcc 6.2-4 64-bit target on x86-64 Linux
Copyright 1989-2000, The Portland Group, Inc.  All Rights Reserved.
Copyright 2000-2006, STMicroelectronics, Inc.  All Rights Reserved.
[15:56:46]arthur@tantal238:~/tantale/src/test$ pgcc -o hello-6.2 hello.c
[15:56:53]arthur@tantal238:~/tantale/src/test$ ls -alh hello-*
-rwxr-xr-x  1 arthur gerance 6.8K Oct 23 15:55 hello-6.1
-rwxr-xr-x  1 arthur gerance  71K Oct 23 15:56 hello-6.2

Even with a simple hello world, the size has been multiplied by 10…
What has happened between these two releases ? Or what am I doing wrong ?

Thanks in advance,
Arthur Petitpierre

Arthur-

Yes. T here has been a change between 6.1 and 6.2. For each subroutine, there
is now a .pgi_trace section that supports a coredump trace back facility. We
also link in the required library support routines. At the moment, there is no
way to turn this facility off. However, the size of your executable will be
greatly reduced with release 7.0 - we’ve trimmed things down quite a bit.

If executable size is an issue for you and this is not an acceptable solution,
please email trs@pgroup.com so that we may file a bug and track your request.

Ok, but if it is debugging informations, what is the need to turn it on even if the user does not specify -g when compiling ? There really should be a way to turn it off.
It’s not blocking, but I find it pretty annoying, moreother I have seen nothing about this in the release notes…
But thanks for your quick reply.
Arthur Petitpierre.