Re: transaction_safe exceptions prevent libstdc++ building for some targets

2017-01-20 Thread Jonathan Wakely
On 19/01/17 12:05 +, Joe Seymour wrote: Here's the patch I'm proposing. I've tested it as follows: - msp430-elf no longer encounters the error when configuring libstdc++-v3. Note that libstdc++-v3 doesn't build due to an ICE though. - Configuring libstdc++-v3 for x86_64-unknown-linux-gnu p

Re: transaction_safe exceptions prevent libstdc++ building for some targets

2017-01-19 Thread Joe Seymour
On 18/01/2017 19:24, DJ Delorie wrote: > Joe Seymour writes: >>> the msp430 -mlarge multilib failing to build with... configure: error: Unknown underlying type for size_t make[1]: *** [configure-target-libstdc++-v3] Error 1 >> >> This is still reproducible. > > FYI the underlying type i

Re: transaction_safe exceptions prevent libstdc++ building for some targets

2017-01-18 Thread DJ Delorie
Joe Seymour writes: >> the msp430 -mlarge multilib failing to build with... >>> configure: error: Unknown underlying type for size_t >>> make[1]: *** [configure-target-libstdc++-v3] Error 1 > > This is still reproducible. FYI the underlying type is uint20_t I think I've complained that libstdc++

Re: transaction_safe exceptions prevent libstdc++ building for some targets

2017-01-18 Thread Joe Seymour
On 17/08/2016 12:19, Joe Seymour wrote: > fail to build with... > >> ../../../../../libstdc++-v3/src/c++11/cow-stdexcept.cc:274:3: error: static >> assertion failed: Pointers must be 32 bits or 64 bits wide >> static_assert(sizeof(uint64_t) == sizeof(void*) > > The assert fails because msp430 h

Re: transaction_safe exceptions prevent libstdc++ building for some targets

2016-08-17 Thread Joe Seymour
On 17/08/2016 12:30, Jonathan Wakely wrote: > On 17/08/16 12:19 +0100, Joe Seymour wrote: >> Disabling the original changes for targets with unsupported pointer sizes >> seems >> like a reasonable solution to me, but I can't see an existing mechanism to do >> so? Do others agree? > > Yes, the int

Re: transaction_safe exceptions prevent libstdc++ building for some targets

2016-08-17 Thread Jonathan Wakely
On 17/08/16 12:19 +0100, Joe Seymour wrote: Disabling the original changes for targets with unsupported pointer sizes seems like a reasonable solution to me, but I can't see an existing mechanism to do so? Do others agree? Yes, the intention was that the transaction-safe exceptions would only

transaction_safe exceptions prevent libstdc++ building for some targets

2016-08-17 Thread Joe Seymour
../configure --target=msp430-elf --enable-languages=c,c++ && make -j4 Results in the msp430 -mlarge multilib failing to build with... > configure: error: Unknown underlying type for size_t > make[1]: *** [configure-target-libstdc++-v3] Error 1 This relates to... > commit 13143e139230dc4d72710a