This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [pch-branch] missing binary operator issue.
- From: Karel Gardas <kgardas at objectsecurity dot com>
- To: Geoff Keating <geoffk at geoffk dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 8 Jan 2003 13:18:17 +0100 (CET)
- Subject: Re: [pch-branch] missing binary operator issue.
On Tue, 7 Jan 2003, Geoff Keating wrote:
>
> > /tmp/cczg5mr7.s:2963: Error: symbol `.LCFI0' is already defined
> ...
> > /tmp/cczg5mr7.s:2973: Error: symbol `.L2' is already defined
>
> This patch might fix this problem. Could you test it?
>
No it doesn't. Still I get:
thinkpad:~/arch/devel/mico-devel/orb$ c++ -I../include -Wall -DFAST_PCH -fpermissive -DPIC -fPIC -c orb_pch.h
../include/mico/code_set_registry.h:5:
warning: `CORBA::Codeset::Info
_osf_cs_reg[193]' defined but not used
thinkpad:~/arch/devel/mico-devel/orb$
thinkpad:~/arch/devel/mico-devel/orb$
make c++ -I../include -Wall -DFAST_PCH -fpermissive -DPIC -fPIC -c
os-unix.cc -o os-unix.pic.o
../include/mico/code_set_registry.h:5: warning: `CORBA::Codeset::Info
_osf_cs_reg[193]' defined but not used
/tmp/cctHJBgN.s: Assembler messages:
/tmp/cctHJBgN.s:2973: Error: symbol `.L2' is already defined
/tmp/cctHJBgN.s:2985: Error: symbol `.L4' is already defined
/tmp/cctHJBgN.s:2999: Error: symbol `.L6' is already defined
/tmp/cctHJBgN.s:3033: Error: symbol `.L10' is already defined
/tmp/cctHJBgN.s:3039: Error: symbol `.L11' is already defined
/tmp/cctHJBgN.s:3090: Error: symbol `.L15' is already defined
/tmp/cctHJBgN.s:3104: Error: symbol `.L8' is already defined
/tmp/cctHJBgN.s:3155: Error: symbol `.LEHB0' is already defined
/tmp/cctHJBgN.s:3157: Error: symbol `.LEHE0' is already defined
/tmp/cctHJBgN.s:3173: Error: symbol `.LEHB1' is already defined
/tmp/cctHJBgN.s:3181: Error: symbol `.LEHE1' is already defined
/tmp/cctHJBgN.s:3214: Error: symbol `.LEHB2' is already defined
/tmp/cctHJBgN.s:3216: Error: symbol `.LEHE2' is already defined
make: *** [os-unix.pic.o] Error 1
> I know there are other problems with DWARF2 output, so I don't promise
> the resulting DWARF2 is correct, but it should at least assemble.
>
> It'd be good if you could provide a small test case that triggers the
> problem, I didn't manage to generate one.
I'll try, but IMHO it's quite hard. Do you have any advice which can help
me with it?
Thanks,
Karel
PS: I've used CVS sources 3 hours old + your patch.
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com