public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dk@artimi.com>
To: <gcc@gcc.gnu.org>
Subject: RE: ACATS
Date: Thu, 29 Apr 2004 18:32:00 -0000	[thread overview]
Message-ID: <NUTMEGPuYnYJbXmZoGA000000ca@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <200404290958.47622.john@johnrshannon.com>

> -----Original Message-----
> From: gcc-owner On Behalf Of John R. Shannon
> Sent: 29 April 2004 16:59

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Thank you. I have a case of '.L124' being reference where it 
> should be '.L123'.


  Ouch.  Grep the source for ASM_OUTPUT_INTERNAL_LABEL where the second
parameter is "L", and you'll see that these are generated in final_scan_insn
in final.c, using CODE_LABEL_NUMBER (insn).  However defaults.h also
implements default definitions of ASM_OUTPUT_ADDR_VEC_ELT and
ASM_OUTPUT_DEBUG_LABEL from ASM_OUTPUT_INTERNAL_LABEL.  So your problem may
be specifically related either to switch....case constructs, or to debug
info, or your problem may be more generic.  What's actually at .L123 ?

  The problem seems likely to be that either the CODE_LABEL_NUMBER field of
the insn is getting stomped on, or something is damaging the operand of the
reference in the label_ref.  It might become clear which by following the
rtl dumps through the various stages; or it might be something you can
locate easily by setting a watchpoint or two with gdb.  I'd suspect
something going wrong when insns get deleted, myself.



    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2004-04-29 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 13:12 ACATS John R. Shannon
2004-04-29 13:44 ` ACATS Dave Korn
2004-04-29 13:55   ` ACATS John R. Shannon
2004-04-29 14:10     ` ACATS Dave Korn
2004-04-29 17:11       ` ACATS John R. Shannon
2004-04-29 18:32         ` Dave Korn [this message]
2004-04-29 18:46           ` ACATS John R. Shannon
  -- strict thread matches above, loose matches on Subject: below --
2004-04-29 21:14 ACATS Richard Kenner
2004-04-30  1:48 ` ACATS Zack Weinberg
2004-05-03 20:39   ` ACATS Mark Mitchell
2004-04-29 20:55 ACATS Richard Kenner
2004-04-29 19:46 ACATS Richard Kenner
2004-04-29 20:46 ` ACATS John R. Shannon
2001-12-06 15:12 ACATS Richard Kenner
2001-12-06 15:08 ACATS Richard Kenner
2001-12-06 14:32 ACATS guerby
2001-12-06 15:00 ` ACATS Joseph S. Myers
2001-12-06 15:06   ` ACATS Florian Weimer

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=NUTMEGPuYnYJbXmZoGA000000ca@NUTMEG.CAM.ARTIMI.COM \
    --to=dk@artimi.com \
    --cc=gcc@gcc.gnu.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).