Although I don't believe this is a regression, I do believe it's a bug which
should
ideally be remedied as soon as reasonably possible; as it seems unreasonable to
require any target to support data types more than twice as large as it's
pointer
type, or required by the language standards; so feel that this should be
considered
a reasonably important failure to remedy.
To demonstrate this bug, simply reduce the defined long long size in avr.h to
the
size of a long which is defined as being 32-bits; resulting in:
In file included from /Applications/avr/avr-src/gcc/unwind-dw2.c:36:
/Applications/avr/avr-src/gcc/unwind.h:59: error: unable to emulate 'DI'
In file included from /Applications/avr/avr-src/gcc/unwind-dw2.c:40:
/Applications/avr/avr-src/gcc/unwind-pe.h: In function
'read_encoded_value_with_base':
/Applications/avr/avr-src/gcc/unwind-pe.h:191: error: unable to emulate 'DI'
/Applications/avr/avr-src/gcc/unwind-pe.h:194: error: unable to emulate 'DI'
make[2]: *** [libgcc/./unwind-dw2.o] Error 1
--
Summary: 4.0 bootstrap unreasonably requires 64-bit target type
mode support.
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schlie at comcast dot net
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: ppc-apple-darwin7.8
GCC host triplet: ppc-apple-darwin7.8
GCC target triplet: avr-unknown-unknown
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20143
