* Does gcc 3.2 branch bootstrap on RedHat 7.3?
@ 2002-10-04 1:59 H. J. Lu
2002-10-04 6:03 ` kwall
2002-10-04 9:51 ` Janis Johnson
0 siblings, 2 replies; 12+ messages in thread
From: H. J. Lu @ 2002-10-04 1:59 UTC (permalink / raw)
To: gcc
With Thu Oct 3 23:25:02 PDT 2002's 3.2 branch, I got
/export/build/gnu/gcc-3.2/build-i686-linux/gcc/xgcc -shared-libgcc -B/export/build/gnu/gcc-3.2/build-i686-linux/gcc/ -nostdinc++ -L/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/src -L/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/src/.libs -B/usr/gcc-3.2/i686-pc-linux-gnu/bin/ -B/usr/gcc-3.2/i686-pc-linux-gnu/lib/ -isystem /usr/gcc-3.2/i686-pc-linux-gnu/include -nostdinc++ -I/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu -I/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include -I/export/gnu/src/gcc-3.2/gcc/libstdc++-v3/libsupc++ -I/export/gnu/src/gcc-3.2/gcc/libstdc++-v3/libmath -g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -c /export/gnu/src/gcc-3.2/gcc/libstdc++-v3/src/ext-inst.cc -fPIC -DPIC -o .libs/ext-inst.o
In file included from /export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/rope:60,
from /export/gnu/src/gcc-3.2/gcc/libstdc++-v3/src/ext-inst.cc:34:
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeConcatenation<char, std::allocator<char> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::_Rope_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::rope<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: base
class `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >' has incomplete
type
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:614: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeLeaf<char, std::allocator<char> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::_Rope_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::rope<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: base
class `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >' has incomplete
type
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:580: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:582: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeFunction<char, std::allocator<char> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::_Rope_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::rope<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: base
class `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >' has incomplete
type
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:649: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:652: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeSubstring<char, std::allocator<char> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<char, std::allocator<char>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::_Rope_base<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from `__gnu_cxx::rope<char, std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2456: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:712: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:715: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
std::allocator<char> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeConcatenation<wchar_t, std::allocator<wchar_t> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::_Rope_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::rope<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: base
class `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >' has
incomplete type
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:614: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeLeaf<wchar_t, std::allocator<wchar_t> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::_Rope_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::rope<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: base
class `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >' has
incomplete type
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:580: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:582: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeFunction<wchar_t, std::allocator<wchar_t> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::_Rope_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::rope<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: base
class `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >' has
incomplete type
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:649: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:652: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h: In instantiation of `__gnu_cxx::_Rope_RopeSubstring<wchar_t, std::allocator<wchar_t> >':
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:455: instantiated from `__gnu_cxx::_Rope_rep_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_rep_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_RopeRep<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:1200: instantiated from `__gnu_cxx::_Rope_alloc_base<wchar_t, std::allocator<wchar_t>, true>'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::_Rope_base<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from `__gnu_cxx::rope<wchar_t, std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:2461: instantiated from here
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:712: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:715: no
type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<wchar_t,
std::allocator<wchar_t> >'
make[6]: *** [ext-inst.lo] Error 1
make[6]: Leaving directory `/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/src'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3'
make[4]: *** [all-recursive-am] Error 2
make[4]: Leaving directory `/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3'
make[3]: *** [all-target-libstdc++-v3] Error 2
make[3]: Leaving directory `/export/build/gnu/gcc-3.2/build-i686-linux'
make[2]: *** [bootstrap] Error 2
make[2]: Leaving directory `/export/build/gnu/gcc-3.2/build-i686-linux'
Command exited with non-zero status 2
870.99user 57.15system 28:55.73elapsed 53%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3213960major+3698494minor)pagefaults 0swaps
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/export/build/gnu/gcc-3.2'
make: *** [all] Error 2
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-04 1:59 Does gcc 3.2 branch bootstrap on RedHat 7.3? H. J. Lu
@ 2002-10-04 6:03 ` kwall
2002-10-04 9:51 ` Janis Johnson
1 sibling, 0 replies; 12+ messages in thread
From: kwall @ 2002-10-04 6:03 UTC (permalink / raw)
To: H. J. Lu; +Cc: gcc
On Thu, Oct 03, 2002 at 11:59:22PM -0700, H. J. Lu wrote:
> With Thu Oct 3 23:25:02 PDT 2002's 3.2 branch, I got
[...]
I've gotten it to bootstrap here on several occasions.
Kurt
--
Just remember: when you go to court, you are trusting your fate to
twelve people that weren't smart enough to get out of jury duty!
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-04 1:59 Does gcc 3.2 branch bootstrap on RedHat 7.3? H. J. Lu
2002-10-04 6:03 ` kwall
@ 2002-10-04 9:51 ` Janis Johnson
2002-10-04 9:56 ` H. J. Lu
1 sibling, 1 reply; 12+ messages in thread
From: Janis Johnson @ 2002-10-04 9:51 UTC (permalink / raw)
To: H. J. Lu; +Cc: gcc
On Thu, Oct 03, 2002 at 11:59:22PM -0700, H. J. Lu wrote:
> With Thu Oct 3 23:25:02 PDT 2002's 3.2 branch, I got
>
> /export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
> type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
> std::allocator<char> >'
I got the same failure last night on ia64-unknown-linux-gnu with the
3.2 branch.
Janis
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-04 9:51 ` Janis Johnson
@ 2002-10-04 9:56 ` H. J. Lu
2002-10-04 10:05 ` H. J. Lu
2002-10-05 3:33 ` Does gcc 3.2 branch bootstrap on RedHat 7.3? Andreas Tobler
0 siblings, 2 replies; 12+ messages in thread
From: H. J. Lu @ 2002-10-04 9:56 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc, mark
On Fri, Oct 04, 2002 at 09:45:56AM -0700, Janis Johnson wrote:
> On Thu, Oct 03, 2002 at 11:59:22PM -0700, H. J. Lu wrote:
> > With Thu Oct 3 23:25:02 PDT 2002's 3.2 branch, I got
> >
> > /export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
> > type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
> > std::allocator<char> >'
>
> I got the same failure last night on ia64-unknown-linux-gnu with the
> 3.2 branch.
>
Mark, Andreas has identified your patch breaks both mainline and 3.2:
http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
Shouldn't we revert it at least on the 3.2 branch?
H.J.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-04 9:56 ` H. J. Lu
@ 2002-10-04 10:05 ` H. J. Lu
2002-10-04 11:43 ` PATCH: Revert part of c++ change (Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?) H. J. Lu
2002-10-05 3:33 ` Does gcc 3.2 branch bootstrap on RedHat 7.3? Andreas Tobler
1 sibling, 1 reply; 12+ messages in thread
From: H. J. Lu @ 2002-10-04 10:05 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc, mark, gcc-patches
On Fri, Oct 04, 2002 at 09:47:24AM -0700, H. J. Lu wrote:
> On Fri, Oct 04, 2002 at 09:45:56AM -0700, Janis Johnson wrote:
> > On Thu, Oct 03, 2002 at 11:59:22PM -0700, H. J. Lu wrote:
> > > With Thu Oct 3 23:25:02 PDT 2002's 3.2 branch, I got
> > >
> > > /export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
> > > type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
> > > std::allocator<char> >'
> >
> > I got the same failure last night on ia64-unknown-linux-gnu with the
> > 3.2 branch.
> >
>
> Mark, Andreas has identified your patch breaks both mainline and 3.2:
>
> http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
>
> Shouldn't we revert it at least on the 3.2 branch?
>
Since Mark is out of office from October 3rd through October 7th, I
guess someone else has to fix/revert the 3.2 branch. If noone does
before 11pm PDT Oct. 4, 2002, I will do it.
H.J.
^ permalink raw reply [flat|nested] 12+ messages in thread
* PATCH: Revert part of c++ change (Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?)
2002-10-04 10:05 ` H. J. Lu
@ 2002-10-04 11:43 ` H. J. Lu
0 siblings, 0 replies; 12+ messages in thread
From: H. J. Lu @ 2002-10-04 11:43 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc, mark, gcc-patches
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Fri, Oct 04, 2002 at 09:55:51AM -0700, H. J. Lu wrote:
> On Fri, Oct 04, 2002 at 09:47:24AM -0700, H. J. Lu wrote:
> > On Fri, Oct 04, 2002 at 09:45:56AM -0700, Janis Johnson wrote:
> > > On Thu, Oct 03, 2002 at 11:59:22PM -0700, H. J. Lu wrote:
> > > > With Thu Oct 3 23:25:02 PDT 2002's 3.2 branch, I got
> > > >
> > > > /export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
> > > > type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
> > > > std::allocator<char> >'
> > >
> > > I got the same failure last night on ia64-unknown-linux-gnu with the
> > > 3.2 branch.
> > >
> >
> > Mark, Andreas has identified your patch breaks both mainline and 3.2:
> >
> > http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
> >
> > Shouldn't we revert it at least on the 3.2 branch?
> >
>
> Since Mark is out of office from October 3rd through October 7th, I
> guess someone else has to fix/revert the 3.2 branch. If noone does
> before 11pm PDT Oct. 4, 2002, I will do it.
>
I checked in the patch enclosed here to the the 3.2 branch. The test
result is at
http://gcc.gnu.org/ml/gcc-testresults/2002-10/msg00119.html
2002-10-04 H.J. Lu (hjl@gnu.org)
* pt.c (tsubst_decl, case VAR_DECL): Back out the last change.
(tsubst_expr, case DECL_STMT): Likewise.
H.J.
[-- Attachment #2: gcc-mark-c++.patch --]
[-- Type: text/plain, Size: 2861 bytes --]
2002-10-04 H.J. Lu (hjl@gnu.org)
* pt.c (tsubst_decl, case VAR_DECL): Back out the last change.
(tsubst_expr, case DECL_STMT): Likewise.
Index: gcc/cp/pt.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cp/pt.c,v
retrieving revision 1.578.2.11.2.1
retrieving revision 1.578.2.11.2.2
diff -u -p -r1.578.2.11.2.1 -r1.578.2.11.2.2
--- gcc/cp/pt.c 3 Oct 2002 06:54:59 -0000 1.578.2.11.2.1
+++ gcc/cp/pt.c 4 Oct 2002 05:25:15 -0000 1.578.2.11.2.2
@@ -6079,7 +6079,7 @@ tsubst_decl (t, args, type, complain)
}
r = copy_decl (t);
- TREE_TYPE (r) = type;
+ TREE_TYPE (r) = complete_type (type);
c_apply_type_quals_to_decl (cp_type_quals (type), r);
DECL_CONTEXT (r) = ctx;
/* Clear out the mangled name and RTL for the instantiation. */
@@ -6115,6 +6115,8 @@ tsubst_decl (t, args, type, complain)
TREE_CHAIN (r) = NULL_TREE;
if (TREE_CODE (r) == VAR_DECL && VOID_TYPE_P (type))
cp_error_at ("instantiation of `%D' as type `%T'", r, type);
+ /* Compute the size, alignment, etc. of R. */
+ layout_decl (r, 0);
}
break;
@@ -7374,9 +7376,6 @@ tsubst_expr (t, args, complain, in_decl)
decl = tsubst (decl, args, complain, in_decl);
if (decl != error_mark_node)
{
- if (TREE_CODE (decl) != TYPE_DECL)
- /* Make sure the type is instantiated now. */
- complete_type (TREE_TYPE (decl));
if (init)
DECL_INITIAL (decl) = error_mark_node;
/* By marking the declaration as instantiated, we avoid
@@ -7386,19 +7385,26 @@ tsubst_expr (t, args, complain, in_decl)
do. */
if (TREE_CODE (decl) == VAR_DECL)
DECL_TEMPLATE_INSTANTIATED (decl) = 1;
- maybe_push_decl (decl);
- if (DECL_PRETTY_FUNCTION_P (decl))
+ if (TREE_CODE (decl) == VAR_DECL
+ && ANON_AGGR_TYPE_P (TREE_TYPE (decl)))
+ /* Anonymous aggregates are a special case. */
+ finish_anon_union (decl);
+ else
{
- /* For __PRETTY_FUNCTION__ we have to adjust the
- initializer. */
- const char *const name
- = (*decl_printable_name) (current_function_decl, 2);
- init = cp_fname_init (name);
- TREE_TYPE (decl) = TREE_TYPE (init);
+ maybe_push_decl (decl);
+ if (DECL_PRETTY_FUNCTION_P (decl))
+ {
+ /* For __PRETTY_FUNCTION__ we have to adjust the
+ initializer. */
+ const char *const name
+ = (*decl_printable_name) (current_function_decl, 2);
+ init = cp_fname_init (name);
+ TREE_TYPE (decl) = TREE_TYPE (init);
+ }
+ else
+ init = tsubst_expr (init, args, complain, in_decl);
+ cp_finish_decl (decl, init, NULL_TREE, 0);
}
- else
- init = tsubst_expr (init, args, complain, in_decl);
- cp_finish_decl (decl, init, NULL_TREE, 0);
}
}
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-04 9:56 ` H. J. Lu
2002-10-04 10:05 ` H. J. Lu
@ 2002-10-05 3:33 ` Andreas Tobler
2002-10-05 4:00 ` Andreas Jaeger
1 sibling, 1 reply; 12+ messages in thread
From: Andreas Tobler @ 2002-10-05 3:33 UTC (permalink / raw)
To: gcc; +Cc: mark
H. J. Lu wrote:
>>>/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
>>> type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char,
>>> std::allocator<char> >'
[]
> Mark, Andreas has identified your patch breaks both mainline and 3.2:
>
> http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
>
> Shouldn't we revert it at least on the 3.2 branch?
What is about the trunk? Do we wait?
Thanks,
Andreas
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-05 3:33 ` Does gcc 3.2 branch bootstrap on RedHat 7.3? Andreas Tobler
@ 2002-10-05 4:00 ` Andreas Jaeger
2002-10-05 11:21 ` Fergus Henderson
0 siblings, 1 reply; 12+ messages in thread
From: Andreas Jaeger @ 2002-10-05 4:00 UTC (permalink / raw)
To: Andreas Tobler; +Cc: gcc, mark
Andreas Tobler <toa@pop.agri.ch> writes:
> H. J. Lu wrote:
>
>>>>/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
>>>> type named `allocator_type' in `struct
>>>> __gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
> []
>> Mark, Andreas has identified your patch breaks both mainline and 3.2:
>> http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
>> Shouldn't we revert it at least on the 3.2 branch?
>
> What is about the trunk? Do we wait?
According to our development rules, we wait 48 hours and then even
need some approval of two other developers:
If a patch is committed which introduces a regression [1], on any
target which the Steering Committee considers to be important [2],
and the problem is reported to the original poster, and 48 hours
pass without either the original poster or any other party
indicating that a fix will be forthcoming in the very near future,
and two people with write privileges to the affected area of the
compiler determine that the best course of action is to revert the
patch, then they may revert the patch.
But I do expect that Mark will be back from vacation on the 8th and
fix it immediatly. The question is whether we wait so long or not.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-05 4:00 ` Andreas Jaeger
@ 2002-10-05 11:21 ` Fergus Henderson
2002-10-05 13:56 ` Andreas Jaeger
2002-10-08 3:02 ` Mark Mitchell
0 siblings, 2 replies; 12+ messages in thread
From: Fergus Henderson @ 2002-10-05 11:21 UTC (permalink / raw)
To: Andreas Jaeger; +Cc: Andreas Tobler, gcc, mark
On 05-Oct-2002, Andreas Jaeger <aj@suse.de> wrote:
> Andreas Tobler <toa@pop.agri.ch> writes:
>
> > H. J. Lu wrote:
> >
> >>>>/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
> >>>> type named `allocator_type' in `struct
> >>>> __gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
> > []
> >> Mark, Andreas has identified your patch breaks both mainline and 3.2:
> >> http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
> >> Shouldn't we revert it at least on the 3.2 branch?
> >
> > What is about the trunk? Do we wait?
>
> According to our development rules, we wait 48 hours and then even
> need some approval of two other developers:
>
> If a patch is committed which introduces a regression [1], on any
> target which the Steering Committee considers to be important [2],
> and the problem is reported to the original poster, and 48 hours
> pass without either the original poster or any other party
> indicating that a fix will be forthcoming in the very near future,
> and two people with write privileges to the affected area of the
> compiler determine that the best course of action is to revert the
> patch, then they may revert the patch.
>
> But I do expect that Mark will be back from vacation on the 8th and
> fix it immediatly. The question is whether we wait so long or not.
I think it would be best to revert it now.
Mark can easily reapply it once it is fixed.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-05 11:21 ` Fergus Henderson
@ 2002-10-05 13:56 ` Andreas Jaeger
2002-10-06 0:12 ` Fergus Henderson
2002-10-08 3:02 ` Mark Mitchell
1 sibling, 1 reply; 12+ messages in thread
From: Andreas Jaeger @ 2002-10-05 13:56 UTC (permalink / raw)
To: Fergus Henderson; +Cc: Andreas Tobler, gcc, mark
Fergus Henderson <fjh@cs.mu.OZ.AU> writes:
> On 05-Oct-2002, Andreas Jaeger <aj@suse.de> wrote:
>> Andreas Tobler <toa@pop.agri.ch> writes:
>>
>> > H. J. Lu wrote:
>> >
>> >>>>/export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
>> >>>> type named `allocator_type' in `struct
>> >>>> __gnu_cxx::_Rope_rep_base<char, std::allocator<char> >'
>> > []
>> >> Mark, Andreas has identified your patch breaks both mainline and 3.2:
>> >> http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html
>> >> Shouldn't we revert it at least on the 3.2 branch?
>> >
>> > What is about the trunk? Do we wait?
>>
>> According to our development rules, we wait 48 hours and then even
>> need some approval of two other developers:
>>
>> If a patch is committed which introduces a regression [1], on any
>> target which the Steering Committee considers to be important [2],
>> and the problem is reported to the original poster, and 48 hours
>> pass without either the original poster or any other party
>> indicating that a fix will be forthcoming in the very near future,
>> and two people with write privileges to the affected area of the
>> compiler determine that the best course of action is to revert the
>> patch, then they may revert the patch.
>>
>> But I do expect that Mark will be back from vacation on the 8th and
>> fix it immediatly. The question is whether we wait so long or not.
>
> I think it would be best to revert it now.
> Mark can easily reapply it once it is fixed.
Yes, he can. But look at the rules above. So, unless two developer
with write privileges to this area approve of this, our rules do not
allow such reversal. And only 24 hours have passed since my email
pointing out the patch.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-05 13:56 ` Andreas Jaeger
@ 2002-10-06 0:12 ` Fergus Henderson
0 siblings, 0 replies; 12+ messages in thread
From: Fergus Henderson @ 2002-10-06 0:12 UTC (permalink / raw)
To: Andreas Jaeger; +Cc: Andreas Tobler, gcc, mark
On 05-Oct-2002, Andreas Jaeger <aj@suse.de> wrote:
> Fergus Henderson <fjh@cs.mu.OZ.AU> writes:
> >
> > I think it would be best to revert it now.
> > Mark can easily reapply it once it is fixed.
>
> Yes, he can. But look at the rules above.
What I'm saying is that if the rules mean that the CVS sources remain
unbootstrappable for significant periods of time even when this could
be easily rectified, then IMHO the rules ought to be changed.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
2002-10-05 11:21 ` Fergus Henderson
2002-10-05 13:56 ` Andreas Jaeger
@ 2002-10-08 3:02 ` Mark Mitchell
1 sibling, 0 replies; 12+ messages in thread
From: Mark Mitchell @ 2002-10-08 3:02 UTC (permalink / raw)
To: Fergus Henderson, Andreas Jaeger; +Cc: Andreas Tobler, gcc
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Gentlemen --
I am confused as to why I did not see that problem.
I apologize for causing so much chaos. I appreciate your reverting the
patch.
I am still stuck on the other end of a modem link; my connection
went awry and I am getting to spend the night in Phoenix.
I am virtually positive that the attached will be the fix, relative to
current mainline sources, and am doing the full bootstrap thing as we
speak. (There was a switch fall-through that I did not see.)
Hopefully I will get this checked in before my morning flight.
Apologetically,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
[-- Attachment #2: Type: text/plain, Size: 6177 bytes --]
Index: decl2.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cp/decl2.c,v
retrieving revision 1.565
diff -c -5 -p -r1.565 decl2.c
*** decl2.c 7 Oct 2002 09:49:18 -0000 1.565
--- decl2.c 8 Oct 2002 08:14:01 -0000
*************** finish_anon_union (anon_union_decl)
*** 1380,1409 ****
{
error ("namespace-scope anonymous aggregates must be static");
return;
}
! main_decl = build_anon_union_vars (anon_union_decl,
! &DECL_ANON_UNION_ELEMS (anon_union_decl),
! static_p, external_p);
!
! if (main_decl == NULL_TREE)
{
! warning ("anonymous aggregate with no members");
! return;
! }
! if (static_p)
! {
! make_decl_rtl (main_decl, 0);
! COPY_DECL_RTL (main_decl, anon_union_decl);
! expand_anon_union_decl (anon_union_decl,
! NULL_TREE,
! DECL_ANON_UNION_ELEMS (anon_union_decl));
}
! else
! add_decl_stmt (anon_union_decl);
}
/* Finish processing a builtin type TYPE. It's name is NAME,
its fields are in the array FIELDS. LEN is the number of elements
in FIELDS minus one, or put another way, it is the maximum subscript
--- 1380,1414 ----
{
error ("namespace-scope anonymous aggregates must be static");
return;
}
! if (!processing_template_decl)
{
! main_decl
! = build_anon_union_vars (anon_union_decl,
! &DECL_ANON_UNION_ELEMS (anon_union_decl),
! static_p, external_p);
!
! if (main_decl == NULL_TREE)
! {
! warning ("anonymous aggregate with no members");
! return;
! }
! if (static_p)
! {
! make_decl_rtl (main_decl, 0);
! COPY_DECL_RTL (main_decl, anon_union_decl);
! expand_anon_union_decl (anon_union_decl,
! NULL_TREE,
! DECL_ANON_UNION_ELEMS (anon_union_decl));
! return;
! }
}
!
! add_decl_stmt (anon_union_decl);
}
/* Finish processing a builtin type TYPE. It's name is NAME,
its fields are in the array FIELDS. LEN is the number of elements
in FIELDS minus one, or put another way, it is the maximum subscript
Index: pt.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cp/pt.c,v
retrieving revision 1.622
diff -c -5 -p -r1.622 pt.c
*** pt.c 7 Oct 2002 09:49:18 -0000 1.622
--- pt.c 8 Oct 2002 08:14:34 -0000
*************** tsubst_decl (t, args, type, complain)
*** 6132,6141 ****
--- 6132,6143 ----
r = spec;
break;
}
r = copy_decl (t);
+ if (TREE_CODE (r) == VAR_DECL)
+ type = complete_type (type);
TREE_TYPE (r) = type;
c_apply_type_quals_to_decl (cp_type_quals (type), r);
DECL_CONTEXT (r) = ctx;
/* Clear out the mangled name and RTL for the instantiation. */
SET_DECL_ASSEMBLER_NAME (r, NULL_TREE);
*************** tsubst_decl (t, args, type, complain)
*** 6171,6180 ****
--- 6173,6184 ----
register_local_specialization (r, t);
TREE_CHAIN (r) = NULL_TREE;
if (TREE_CODE (r) == VAR_DECL && VOID_TYPE_P (type))
cp_error_at ("instantiation of `%D' as type `%T'", r, type);
+ /* Compute the size, alignment, etc. of R. */
+ layout_decl (r, 0);
}
break;
default:
abort ();
*************** tsubst_expr (t, args, complain, in_decl)
*** 7422,7456 ****
{
init = DECL_INITIAL (decl);
decl = tsubst (decl, args, complain, in_decl);
if (decl != error_mark_node)
{
- if (TREE_CODE (decl) != TYPE_DECL)
- /* Make sure the type is instantiated now. */
- complete_type (TREE_TYPE (decl));
if (init)
DECL_INITIAL (decl) = error_mark_node;
/* By marking the declaration as instantiated, we avoid
trying to instantiate it. Since instantiate_decl can't
handle local variables, and since we've already done
all that needs to be done, that's the right thing to
do. */
if (TREE_CODE (decl) == VAR_DECL)
DECL_TEMPLATE_INSTANTIATED (decl) = 1;
! maybe_push_decl (decl);
! if (DECL_PRETTY_FUNCTION_P (decl))
{
! /* For __PRETTY_FUNCTION__ we have to adjust the
! initializer. */
! const char *const name
! = cxx_printable_name (current_function_decl, 2);
! init = cp_fname_init (name);
! TREE_TYPE (decl) = TREE_TYPE (init);
}
- else
- init = tsubst_expr (init, args, complain, in_decl);
- cp_finish_decl (decl, init, NULL_TREE, 0);
}
}
/* A DECL_STMT can also be used as an expression, in the condition
clause of an if/for/while construct. If we aren't followed by
--- 7426,7464 ----
{
init = DECL_INITIAL (decl);
decl = tsubst (decl, args, complain, in_decl);
if (decl != error_mark_node)
{
if (init)
DECL_INITIAL (decl) = error_mark_node;
/* By marking the declaration as instantiated, we avoid
trying to instantiate it. Since instantiate_decl can't
handle local variables, and since we've already done
all that needs to be done, that's the right thing to
do. */
if (TREE_CODE (decl) == VAR_DECL)
DECL_TEMPLATE_INSTANTIATED (decl) = 1;
! if (TREE_CODE (decl) == VAR_DECL
! && ANON_AGGR_TYPE_P (TREE_TYPE (decl)))
! /* Anonymous aggregates are a special case. */
! finish_anon_union (decl);
! else
{
! maybe_push_decl (decl);
! if (DECL_PRETTY_FUNCTION_P (decl))
! {
! /* For __PRETTY_FUNCTION__ we have to adjust the
! initializer. */
! const char *const name
! = cxx_printable_name (current_function_decl, 2);
! init = cp_fname_init (name);
! TREE_TYPE (decl) = TREE_TYPE (init);
! }
! else
! init = tsubst_expr (init, args, complain, in_decl);
! cp_finish_decl (decl, init, NULL_TREE, 0);
}
}
}
/* A DECL_STMT can also be used as an expression, in the condition
clause of an if/for/while construct. If we aren't followed by
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2002-10-08 8:19 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-04 1:59 Does gcc 3.2 branch bootstrap on RedHat 7.3? H. J. Lu
2002-10-04 6:03 ` kwall
2002-10-04 9:51 ` Janis Johnson
2002-10-04 9:56 ` H. J. Lu
2002-10-04 10:05 ` H. J. Lu
2002-10-04 11:43 ` PATCH: Revert part of c++ change (Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?) H. J. Lu
2002-10-05 3:33 ` Does gcc 3.2 branch bootstrap on RedHat 7.3? Andreas Tobler
2002-10-05 4:00 ` Andreas Jaeger
2002-10-05 11:21 ` Fergus Henderson
2002-10-05 13:56 ` Andreas Jaeger
2002-10-06 0:12 ` Fergus Henderson
2002-10-08 3:02 ` Mark Mitchell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).