public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jozef Lawrynowicz <jozef.l@somniumtech.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PING] [MSP430] Trunk patches required for gcc-6-branch to build for msp430
Date: Fri, 26 May 2017 14:44:00 -0000	[thread overview]
Message-ID: <55942e21-bdfd-2214-9509-df68d2910dde@somniumtech.com> (raw)
In-Reply-To: <20170526120135.GF12306@redhat.com>

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. I
> committed both patches you're asking about, but I don't read
> gcc-patches routinely.
> 
>> ---
>>
>> 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 fixes the two
>> build issues, so the build completes successfully.
>>
>> I don't have write access to the GCC repository, so would appreciate
>> if someone could backport these patches to gcc-6-branch if that is 
>> acceptable.
> 
> I've backported both patches, gcc-6-branch should build for you now.
> Please let me know if it doesn't.
> 
> 
Brilliant, the gcc-6-branch builds cleanly for msp430-elf now, thanks!

-bash-4.2$ ./usr/local/bin/msp430-elf-gcc -v
Target: msp430-elf
Configured with: ../configure --target=msp430-elf --enable-languages=c,c++
Thread model: single
gcc version 6.3.1 20170526 (GCC)

      reply	other threads:[~2017-05-26 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 16:19 Jozef Lawrynowicz
2017-05-26 12:26 ` Jonathan Wakely
2017-05-26 14:44   ` Jozef Lawrynowicz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55942e21-bdfd-2214-9509-df68d2910dde@somniumtech.com \
    --to=jozef.l@somniumtech.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).