This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/20675] Small targets without 64 bit long long support are can't bootstrap GCC.
- From: "schlie at comcast dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Mar 2005 03:42:41 -0000
- Subject: [Bug middle-end/20675] Small targets without 64 bit long long support are can't bootstrap GCC.
- References: <20050328234914.20675.schlie@comcast.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From schlie at comcast dot net 2005-03-29 03:42 -------
Subject: Re: Small targets without 64 bit long long
support are can't bootstrap GCC.
> Static debug data should be based on it's required encoding specification,
> and have nothing to do with a target's run-time unwind implementation.
>
> (I'll take a closer look to try to figure out why one is affecting the
> other. However just to double check, is there any reason that a target
> needs to support a data type size that it never references, although
> is statically encoded by the linker into it's debug data section?)
- what appears to be happening is unrelated to the unwind word size; the
stabs data section size is changing when the target's long long size is
reduced to the size of a long, thereby requiring less bytes to represent
leb128 encoded min/max signed/unsigned long long date definitions for the
target; which seems correct; and not related to reducing small target's
unwind word size which should not effect it's dwarf compliance.
(so all seems ok)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20675