-Original Message-
From: Cary Coutant [mailto:ccout...@google.com]
Sent: 09 June 2010 18:43
To: Richard Guenther
Cc: Bingfeng Mei; Jan Hubicka; gcc@gcc.gnu.org
Subject: Re: externally_visible and resoultion file
Yes, this is also what I saw without plugin. I just wonder why
Yes, this is also what I saw without plugin. I just wonder why v
is linked with plugin if resolution file is not used to eliminate need
of externally_visible attribute here.
Probably because of the same linker-plugin bug that causes bar
to be resolved.
Just to make sure I understand the
On Wed, Jun 9, 2010 at 7:43 PM, Cary Coutant ccout...@google.com wrote:
Yes, this is also what I saw without plugin. I just wonder why v
is linked with plugin if resolution file is not used to eliminate need
of externally_visible attribute here.
Probably because of the same linker-plugin
.
Thanks,
Bingfeng
-Original Message-
From: Jan Hubicka [mailto:hubi...@ucw.cz]
Sent: 27 May 2010 09:04
To: Richard Guenther
Cc: Bingfeng Mei; gcc@gcc.gnu.org
Subject: Re: externally_visible and resoultion file
On Wed, May 26, 2010 at 5:53 PM, Bingfeng Mei b...@broadcom.com
wrote
On Tue, Jun 8, 2010 at 3:01 PM, Bingfeng Mei b...@broadcom.com wrote:
Hi,
Sorry for coming back to this issue after a while. I am still puzzled
by this. The following are two test files:
a.c
#include string.h
#include stdio.h
extern int foo(int);
void bar()
{
printf(bar\n);
}
extern
Subject: Re: externally_visible and resoultion file
On Tue, Jun 8, 2010 at 3:01 PM, Bingfeng Mei b...@broadcom.com wrote:
Hi,
Sorry for coming back to this issue after a while. I am still puzzled
by this. The following are two test files:
a.c
#include string.h
#include stdio.h
On Tue, Jun 8, 2010 at 4:15 PM, Bingfeng Mei b...@broadcom.com wrote:
Thanks. But why v is linked correctly here? Shouldn't it
be treated as static with -fwhole-program?
Works for me without the linker plugin as well:
gcc-4.5 -O2 -o t t1.o t2.o -flto -fwhole-program -B
June 2010 15:18
To: Bingfeng Mei
Cc: Jan Hubicka; gcc@gcc.gnu.org; Cary Coutant
Subject: Re: externally_visible and resoultion file
On Tue, Jun 8, 2010 at 4:15 PM, Bingfeng Mei b...@broadcom.com wrote:
Thanks. But why v is linked correctly here? Shouldn't it
be treated as static
that causes bar
to be resolved.
Richard.
Thanks,
Bingfeng
-Original Message-
From: Richard Guenther [mailto:richard.guent...@gmail.com]
Sent: 08 June 2010 15:18
To: Bingfeng Mei
Cc: Jan Hubicka; gcc@gcc.gnu.org; Cary Coutant
Subject: Re: externally_visible and resoultion file
On Wed, May 26, 2010 at 5:53 PM, Bingfeng Mei b...@broadcom.com wrote:
Hi, Richard,
With resolution file generated by GOLD (or I am going to hack gnu LD), is
externally_visible attribute still needed to annotate those symbols accessed
from non-LTO objects when compiling with
On Wed, May 26, 2010 at 5:53 PM, Bingfeng Mei b...@broadcom.com wrote:
Hi, Richard,
With resolution file generated by GOLD (or I am going to hack gnu LD), is
externally_visible attribute still needed to annotate those symbols accessed
from non-LTO objects when compiling with -fwhole-program.
11 matches
Mail list logo
