From: Karel Gardas <kgardas@objectsecurity.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc@gcc.gnu.org
Subject: Re: [pch-branch] missing binary operator issue.
Date: Wed, 08 Jan 2003 16:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.43.0301081314170.7028-100000@thinkpad.c0202001.roe.itnq.net> (raw)
In-Reply-To: <200301071920.h07JK1I04152@desire.geoffk.org>
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
prev parent reply other threads:[~2003-01-08 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 4:04 Karel Gardas
2003-01-02 17:59 ` Geoff Keating
2003-01-02 21:26 ` Karel Gardas
2003-01-02 22:21 ` Andrew Pinski
2003-01-07 19:32 ` Geoff Keating
2003-01-08 16:06 ` Karel Gardas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.43.0301081314170.7028-100000@thinkpad.c0202001.roe.itnq.net \
--to=kgardas@objectsecurity.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).