public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Tobler <andreast-list@fgznet.ch>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [patch][arm][FreeBSD] add support for armv7*-*-freebsd*
Date: Sun, 08 Oct 2017 20:58:00 -0000	[thread overview]
Message-ID: <9239a945-f88e-742a-a23c-6868998b1cef@fgznet.ch> (raw)

Hi all,

I'm going to commit this patch if no objections pop up.

We (FreeBSD folks) have added a new target tripplet for armv7*-*-freebsd*
To be able to build GCC we need the below changes.

Results will be posted to the usual place, once they completed....

While here I remove an obsolete define.

I'll post similar patches for gcc-7, gcc-6 and gcc-5 branches.
They differ a bit...

Please speak up if you do not agree.

TIA,
Andreas

2017-10-08  Andreas Tobler  <andreast@gcc.gnu.org>

	* config.gcc (armv7*-*-freebsd*): New target.
	(armv6*-*-freebsd*): Remove obsolete TARGET_FREEBSD_ARMv6 define.

Index: config.gcc
===================================================================
--- config.gcc	(revision 253528)
+++ config.gcc	(working copy)
@@ -1093,11 +1093,14 @@
  	case $target in
  	armv6*-*-freebsd*)
  	    target_cpu_cname="arm1176jzf-s"
-	    tm_defines="${tm_defines} TARGET_FREEBSD_ARMv6=1"
              if test $fbsd_major -ge 11; then
                 tm_defines="${tm_defines} TARGET_FREEBSD_ARM_HARD_FLOAT=1"
              fi
  	    ;;
+	armv7*-*-freebsd*)
+	    target_cpu_cname="generic-armv7-a"
+	    tm_defines="${tm_defines} TARGET_FREEBSD_ARM_HARD_FLOAT=1"
+	    ;;
  	*)
  	    target_cpu_cname="arm9"
  	    ;;

             reply	other threads:[~2017-10-08 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 20:58 Andreas Tobler [this message]
2017-10-10 18:51 ` Andreas Tobler

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=9239a945-f88e-742a-a23c-6868998b1cef@fgznet.ch \
    --to=andreast-list@fgznet.ch \
    --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).