public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15231] [3.4 only] constant pool entries referring to nonexistent labels
Date: Fri, 02 Sep 2005 22:27:00 -0000	[thread overview]
Message-ID: <20050902222738.2770.qmail@sourceware.org> (raw)
In-Reply-To: <20040430162847.15231.pb@gcc.gnu.org>


------- Additional Comments From rearnsha at gcc dot gnu dot org  2005-09-02 22:27 -------
I've made a small amount of headway on this.

Labels L22 and L21 were (when created) the addresses of objects in the code. 
However, they are deleted (presumably as unreachable), but the references to the
lables persist.

This is presumably exactly the case that RTH believed couldn't happen when he
mentioned this in his email here:

http://gcc.gnu.org/ml/gcc-patches/2000-05/msg00881.html

and the reason we don't abort on ARM is that we never call output_constant_pool
since we roll our own mini-pools.

I've sofar been unsuccessful in reducing the testcase to something more managable.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2005-02-22 04:10:35         |2005-09-02 22:27:33
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15231


  parent reply	other threads:[~2005-09-02 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 16:36 [Bug target/15231] New: " pb at gcc dot gnu dot org
2004-04-30 16:43 ` [Bug target/15231] " pb at gcc dot gnu dot org
2004-05-18 15:27 ` rearnsha at gcc dot gnu dot org
2004-08-13  2:13 ` pinskia at gcc dot gnu dot org
2004-11-15  3:24 ` [Bug target/15231] [3.4 only] " pinskia at gcc dot gnu dot org
2005-05-19 17:53 ` mmitchel at gcc dot gnu dot org
2005-09-02 22:27 ` rearnsha at gcc dot gnu dot org [this message]
     [not found] <bug-15231-592@http.gcc.gnu.org/bugzilla/>
2005-11-21  2:09 ` gdr at gcc dot gnu dot org
2005-11-28 10:22 ` gdr at gcc dot gnu dot org
2006-02-28  9:15 ` gdr at gcc dot gnu dot org

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=20050902222738.2770.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).