From: Jozef Lawrynowicz <jozef.l@somniumtech.com>
To: gcc-patches@gcc.gnu.org
Subject: [PING] [MSP430] Trunk patches required for gcc-6-branch to build for msp430
Date: Mon, 22 May 2017 16:19:00 -0000 [thread overview]
Message-ID: <6c897cac-0a15-7bb3-5e4c-97ce87787272@somniumtech.com> (raw)
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 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.
next reply other threads:[~2017-05-22 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 16:19 Jozef Lawrynowicz [this message]
2017-05-26 12:26 ` Jonathan Wakely
2017-05-26 14:44 ` Jozef Lawrynowicz
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=6c897cac-0a15-7bb3-5e4c-97ce87787272@somniumtech.com \
--to=jozef.l@somniumtech.com \
--cc=gcc-patches@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).