On 26/05/2017 13:01, Jonathan Wakely wrote:
On 22/05/17 17:16 +0100, Jozef Lawrynowicz wrote:
Ping, original post:
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01560.html
These are both libstdc++ patches and originally posted to the
libstdc++ list, so you'll have more luck mailing that list.
On 22/05/17 17:16 +0100, Jozef Lawrynowicz wrote:
Ping, original post:
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01560.html
These are both libstdc++ patches and originally posted to the
libstdc++ list, so you'll have more luck mailing that list. I
committed both patches you're asking
Ping, original post:
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01560.html
---
For the msp430-elf target, the gcc-6-branch fails to build when
configured to enable C++ support.
The gcc-5-branch successfully builds with C++ support.
Backporting r244727 and r243310 to the gcc-6-branch
The gcc-6-branch at the current upstream revision (r246561) doesn't
build when configured with the following options: "--target=msp430-elf
--enable-languages=c,c++"
The gcc-5-branch does build with these options.
Backporting r244727 and r243310 to the gcc-6-branch fixes the two
build issues, so
r244727 and r243310 from the gcc trunk are needed in the gcc-6-branch
to build gcc for the msp430 target with C and C++ support.
Would it be possible for these patches to be backported to the
gcc-6-branch? The gcc-5-branch builds for msp430 with C and C++
support, so isn't this technically a
