From: Nick Clifton <nickc@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Commit: MSP430: Built libgcc with hardware multiply disabled
Date: Thu, 22 May 2014 15:14:00 -0000 [thread overview]
Message-ID: <87mwe9vo9o.fsf@redhat.com> (raw)
Hi Guys,
I am applying the patch below (to mainline and the 4.9 branch) to fix
a problem when building libgcc for the MSP430. The problem was that
the software multiply functions were being renamed to the hardware
multiply equivalents, and libgcc was using the hardware multiply
feature even when it was not clear that it would be supported by the
target MCU. The fix is just to disable the use of hardware multiplies
inside libgcc.
Cheers
Nick
libgcc/ChangeLog
2014-05-22 Nick Clifton <nickc@redhat.com>
* config/msp430/t-msp430 (HOST_LIBGCC2_CFLAGS): Add
-mhwmult=none.
Index: config/msp430/t-msp430
===================================================================
--- config/msp430/t-msp430 (revision 210809)
+++ config/msp430/t-msp430 (working copy)
@@ -42,7 +42,7 @@
$(srcdir)/config/msp430/floathisf.c \
$(srcdir)/config/msp430/cmpd.c
-HOST_LIBGCC2_CFLAGS += -Os -ffunction-sections -fdata-sections
+HOST_LIBGCC2_CFLAGS += -Os -ffunction-sections -fdata-sections -mhwmult=none
# Local Variables:
# mode: Makefile
reply other threads:[~2014-05-22 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mwe9vo9o.fsf@redhat.com \
--to=nickc@redhat.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).