This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/15231] [3.4 only] constant pool entries referring to nonexistent labels
- From: "gdr at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Nov 2005 02:09:03 -0000
- Subject: [Bug target/15231] [3.4 only] constant pool entries referring to nonexistent labels
- References: <bug-15231-592@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from gdr at gcc dot gnu dot org 2005-11-21 02:09 -------
(In reply to comment #5)
> 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.
Have you been able to track this with RTH?
Do you care about this bug be fixed for 3.4.5?
We're in 3.4.6 pre-release business now.
-- Gaby
--
gdr at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rth at gcc dot gnu dot org,
| |gdr at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15231