Re: ACATS

["John R. Shannon" <john at johnrshannon dot com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you. I have a case of '.L124' being reference where it should be 
'.L123'.

On Thursday 29 April 2004 6:45 am, Dave Korn wrote:
> > -----Original Message-----
> > From: gcc-owner On Behalf Of John R. Shannon
> > Sent: 29 April 2004 13:20
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I'm sorry, but I don't understand your reply.
> >
> > On Thursday 29 April 2004 6:13 am, Dave Korn wrote:
> > > > -----Original Message-----
> > > > From: gcc-owner On Behalf Of John R. Shannon
> > > > Sent: 29 April 2004 13:09
> > > > To: gcc@gcc.gnu.org
> > > > Subject: ACATS
> > > >
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > >
> > > > Could someone please point me in the right direction in
> > > > chasing down undefined
> > > > references to `.LC124' and `.LC93' in gnatlink? Off-hand, I
> > > > don't see where
> > > > the references come from.
> > >
> > >  --save-temps
>
> Run your compiles with --save-temps on the command line.  That'll save the
> generated assembler files.  Any label beginning ".LC" is a local label
> (usually a string constant or switch..case jump table); that is, it should
> be both defined and referred to in the same file.  You should be able to
> see if gcc is generating the wrong label in the reference, or is forgetting
> to output the label definition in front of the object it refers to, or if
> they look valid but there's some accident perhaps to do with what section
> they end up in that's confusing the link.
>
>
>     cheers,
>       DaveK

- -- 

John R. Shannon
john@johnrshannon.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iEYEARECAAYFAkCRJjYACgkQOKbCxya4HYtpIACfUTUzhWscVfbX/YEop64T0C1I
wMwAn1H9NvsQkjinPBAIO98QeRulZrkE
=WUjM
-----END PGP SIGNATURE-----