all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Giorgos Keramidas <keramida@freebsd.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	Dan Nicolaescu <dann@ics.uci.edu>,
	emacs-devel@gnu.org
Subject: Re: configure.in support for FreeBSD ia64/sparc64/powerpc
Date: Tue, 30 Dec 2008 00:03:59 +0100	[thread overview]
Message-ID: <18777.22367.789436.254592@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <87r63qa9t5.fsf@kobe.laptop>

>>>>> On Tue, 30 Dec 2008, Giorgos Keramidas wrote:

> On Mon, 29 Dec 2008 14:06:04 -0800 (PST), Dan Nicolaescu <dann@ics.uci.edu> wrote:
>> > Err, I think there's a misunderstanding here.  The src/alloc.c change
>> > is related to sparc64 not Solaris (not _only_ Solaris, that is):
>> 
>> >     --- a/src/alloc.c	Fri Oct 27 15:45:51 2006 +0000
>> >     +++ b/src/alloc.c	Sat Oct 28 01:49:45 2006 +0300
>> >     @@ -4560,7 +4560,11 @@ mark_stack ()
>> >           needed on ia64 too.  See mach_dep.c, where it also says inline
>> >           assembler doesn't work with relevant proprietary compilers.
>> >     */
>> >      #ifdef sparc
>> >     +#ifdef __sparc64__
>> >     +  asm ("flushw");
>> >     +#else
>> >        asm ("ta 3");
>> >     +#endif
>> >      #endif
>> >
>> > Now, I don't think anybody would argue that there are probably far more
>> > Solaris installations of sparc64 than FreeBSD ones.
>> 
>> Exactly, that code has been running for all other systems just fine for
>> many years.  Why the insistence to change without proper testing?
>> Why not just make the conditional
>> defined (__sparc64__) && defined (__FreeBSD__) ?

> My impression from the original Gentoo bug <http://bugs.gentoo.org/159584>
> is that this affects Linux too,

Sparc/Linux is fine, with or without the patch. Looks like both
"flushw" and "ta 3" work there.

> so making the code depend on __FreeBSD__ doesn't solve Ulrich's
> original problem.

It does, in fact. But testing for the OS still looks wrong to me,
since it is a question of a machine instruction implemented for
SPARC-V9, but not for earlier CPUs.

Could the patch be committed with the "&& defined (__FreeBSD__)", and
we keep in mind to remove this piece after the 23.1 release?

Ulrich




  reply	other threads:[~2008-12-29 23:03 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=18777.22367.789436.254592@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.