unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	Giorgos Keramidas <keramida@freebsd.org>,
	emacs-devel@gnu.org
Subject: Re: configure.in support for FreeBSD ia64/sparc64/powerpc
Date: Fri, 19 Dec 2008 19:10:26 +0100	[thread overview]
Message-ID: <18763.58258.187720.412172@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <200812191716.mBJHG0oC016436@mothra.ics.uci.edu>

>>>>> On Fri, 19 Dec 2008, Dan Nicolaescu wrote:

> Was this tested on GNU/Linux

Yes.

> and Solaris (and all other sparc64 platforms)?

No.

> Otherwise better make that #ifdef depend on FreeBSD.

I've nothing against that.

--- emacs-orig/src/alloc.c
+++ emacs/src/alloc.c
@@ -4573,7 +4573,11 @@
      needed on ia64 too.  See mach_dep.c, where it also says inline
      assembler doesn't work with relevant proprietary compilers.  */
 #ifdef __sparc__
+#if defined (__sparc64__) && defined(__FreeBSD__)
+  asm ("flushw");
+#else
   asm ("ta 3");
+#endif
 #endif
 
   /* Save registers that we need to see on the stack.  We need to see




  reply	other threads:[~2008-12-19 18:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 21:45 configure.in support for FreeBSD ia64/sparc64/powerpc Giorgos Keramidas
2006-11-04  3:28 ` Chong Yidong
2006-11-06 14:10   ` Giorgos Keramidas
2008-12-19 13:51     ` Ulrich Mueller
2008-12-19 17:16       ` Dan Nicolaescu
2008-12-19 18:10         ` Ulrich Mueller [this message]
2008-12-19 19:51           ` Giorgos Keramidas
2009-01-22 11:10             ` Ulrich Mueller
2009-01-23  3:31               ` Giorgos Keramidas
2009-01-23  4:39                 ` Chong Yidong
2009-01-23  5:42                   ` Giorgos Keramidas
2009-02-05  6:37                   ` Ulrich Mueller
2009-02-05 13:55                     ` Chong Yidong
2009-02-05 14:17                       ` Giorgos Keramidas
2009-02-05 14:20                       ` Dan Nicolaescu
2009-02-05 15:30                         ` Chong Yidong
2009-02-05 15:31                           ` Dan Nicolaescu
2009-02-05 16:01                             ` Ulrich Mueller
2008-12-21  8:24           ` Ulrich Mueller
2008-12-29 19:42             ` Ulrich Mueller
2008-12-29 19:54               ` Dan Nicolaescu
2008-12-29 20:20                 ` Ulrich Mueller
2008-12-29 20:39                   ` Dan Nicolaescu
2008-12-29 21:19                     ` Ulrich Mueller
2008-12-29 21:41                     ` Giorgos Keramidas
2008-12-29 22:06                       ` Dan Nicolaescu
2008-12-29 22:36                         ` Giorgos Keramidas
2008-12-29 23:03                           ` Ulrich Mueller
2008-12-30  3:47                             ` Dan Nicolaescu
2008-12-30 12:44                               ` Ulrich Mueller
2008-12-30 20:55                                 ` Giorgos Keramidas

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=18763.58258.187720.412172@a1ihome1.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=cyd@stupidchicken.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=keramida@freebsd.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).