This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/41404] expr.c undefined reference while linking jc1
- From: "davek at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Sep 2009 12:32:04 -0000
- Subject: [Bug bootstrap/41404] expr.c undefined reference while linking jc1
- References: <bug-41404-14373@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #14 from davek at gcc dot gnu dot org 2009-09-19 12:32 -------
(In reply to comment #13)
Thanks for taking the time to explain that.
I think the implication of what you're saying is that we can in fact handle
strings and just giving up on them is too severe, but we need to decide
somewhere a bit further up the call stack whether to use the string itself or
the address-of the string as the value in the location table, based on the type
of the var_decl; is that about right?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41404