[Bug middle-end/20675] Small targets without 64 bit long long support are can't bootstrap GCC.

[schlie at comcast dot net]

------- Additional Comments From schlie at comcast dot net  2005-03-29 02:09 -------
Subject: Re:  Small targets without 64 bit long long
 support are can't bootstrap GCC.

>> Also note that the dwarf-2 unwinder needs to be 64bit the last time I looked
>> (I think it is defined by the dwarf-2 standard).
> 
> - From the best I can tell reviewing the standard, it seems fully compatible
>   to limit the target's unwind data type size, to the largest data type it
>   supports; as although a 64-bit data type is defined by the standard,
>   neither a host application or target could validly send, request data
>   sized larger than the largest type defined as supported by the target;
>   nor are large data types required for communicating smaller data type
>   values, as data access is byte not unwind-word offset/size oriented.
> 
>   (so it seems fully compatible from the best I can tell?)

- Actually there may be a problem, as I did notice that the stabs data
  section size was affected by this change, which wouldn't have guessed
  to be affected by the size of the target's run-time unwind word data
  size?

  It seems that GCC may be presuming that the static debug data (which is
  for debugger reference) is using the target's unwind word size; which is
  wrong they are unrelated to each other, although may be the same.

  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?)




-- 


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