From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Noah Lavine Newsgroups: gmane.lisp.guile.bugs Subject: bug#14672: QT port for ARM within guile Date: Fri, 21 Jun 2013 09:42:10 -0400 Message-ID: References: <8D03B9BED2EFC3E-1390-337FC@webmail-vd011.sysops.aol.com> <8D03C5DA0E1DCD7-1900-6DB1@webmail-d222.sysops.aol.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b86f2a2f6bd1304dfaa3bb8 X-Trace: ger.gmane.org 1371822203 17546 80.91.229.3 (21 Jun 2013 13:43:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Jun 2013 13:43:23 +0000 (UTC) Cc: 14672@debbugs.gnu.org To: eactors@aol.com Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Fri Jun 21 15:43:24 2013 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Uq1cW-00016J-3o for guile-bugs@m.gmane.org; Fri, 21 Jun 2013 15:43:20 +0200 Original-Received: from localhost ([::1]:38232 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uq1cV-00011s-NP for guile-bugs@m.gmane.org; Fri, 21 Jun 2013 09:43:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uq1cJ-0000mx-Kf for bug-guile@gnu.org; Fri, 21 Jun 2013 09:43:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uq1cF-0003Pa-7t for bug-guile@gnu.org; Fri, 21 Jun 2013 09:43:07 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:38157) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uq1cF-0003PF-4V for bug-guile@gnu.org; Fri, 21 Jun 2013 09:43:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Uq1cE-0003gp-Im for bug-guile@gnu.org; Fri, 21 Jun 2013 09:43:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noah Lavine Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Fri, 21 Jun 2013 13:43:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14672 X-GNU-PR-Package: guile X-GNU-PR-Keywords: Original-Received: via spool by 14672-submit@debbugs.gnu.org id=B14672.137182215914118 (code B ref 14672); Fri, 21 Jun 2013 13:43:02 +0000 Original-Received: (at 14672) by debbugs.gnu.org; 21 Jun 2013 13:42:39 +0000 Original-Received: from localhost ([127.0.0.1]:60706 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Uq1br-0003fe-3V for submit@debbugs.gnu.org; Fri, 21 Jun 2013 09:42:39 -0400 Original-Received: from mail-pb0-f42.google.com ([209.85.160.42]:47491) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Uq1bo-0003fJ-II for 14672@debbugs.gnu.org; Fri, 21 Jun 2013 09:42:37 -0400 Original-Received: by mail-pb0-f42.google.com with SMTP id un1so7795699pbc.29 for <14672@debbugs.gnu.org>; Fri, 21 Jun 2013 06:42:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=tTKDZkrzGbKhP3cGCck3K3uSW3bCj9Jfba1yLn5Wd3w=; b=g3fRhgAj9J0COzEHKhIRnEyV8sEt5dfPMxdA2xSj9eSeNpRWiu0grbWFPZgzOAoWbJ 2JjLhealixZFmzK8LiI095DKv4fKgQaQbNARi3/ABCoAoAYnIf8n4w8I2SxKFg4obYNU 3WUl+6XBzcUmvqE12fJ7bAIrfk0KmKWTndcKxfXg+5C8kOaV2XullgHk8spAZfiMUJDp /lfVdMkVQuOGIwHCHAZHdlLdY/FtLLmZ9+Pbh23inTrLV2gHk4YgUid4P4R+V7iTqHWm 350oExRuVQ+1gEGmVYTEqsk2ibUzJ4GcPLqc0lY0XeuJBIPkMzZaFZNQ6cvW5mfKoASZ UB0A== X-Received: by 10.68.162.133 with SMTP id ya5mr12332296pbb.110.1371822150301; Fri, 21 Jun 2013 06:42:30 -0700 (PDT) Original-Received: by 10.68.91.1 with HTTP; Fri, 21 Jun 2013 06:42:10 -0700 (PDT) In-Reply-To: <8D03C5DA0E1DCD7-1900-6DB1@webmail-d222.sysops.aol.com> X-Google-Sender-Auth: w5_GBStEYB3fgXAUq3rQrv615sU X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:7184 Archived-At: --047d7b86f2a2f6bd1304dfaa3bb8 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm afraid I don't know anything about it then. I doubt it's in Guile now. Best, Noah On Fri, Jun 21, 2013 at 2:13 AM, wrote: > QT stands for QuickThreads, and in some cases is a massive speed > improvement. There was a technical paper on this back in the 94 called > "Tools and Techniques for Building Fast Portable Thread Packages". > On an x86-architecture this speeds up SystemC by a factor of 40 (Linux > Ubuntu). And I believe it will increase the arm speed by at least 500% fo= r > my use case. Since the content switch isn=92t that big for the arm having > less registers to save compared to the x86. > So QT should always be considered if available, but somehow it seems to > pass into oblivion. > Cheers > eactor > > > -----Original Message----- > From: Noah Lavine > To: eactors > Cc: 14672 <14672@debbugs.gnu.org> > Sent: Thu, Jun 20, 2013 11:25 pm > Subject: Re: bug#14672: QT port for ARM within guile > > Hello, > > Excuse my ignorance, but what is a "QT"? I can tell you're not referring > to the widget toolkit. > > Also, I believe Guile uses pthreads on most platforms, so if you're > running Linux on ARM (which is the common case on ARM nowadays, I think), > you should have threads. Unless you want userspace threads. > > Best, > Noah > > > On Thu, Jun 20, 2013 at 12:07 AM, wrote: > >> Hello, >> I found a quick thread implementation for ARM within the guile svn: ( >> http://git.savannah.gnu.org/gitweb/?p=3Dguile.git;a=3Dtree;f=3Dqt;h=3Dc9= 8346f9299df235964738dbf4b87da9806c9f52;hb=3D72e4a3b1df86fdfca752221716c3e3f= 5573ff6a5 >> >> Hope you can help me with this. Do you know what the status of this >> port was? Did it work? I would like to add a QT for ARM into the SystemC >> Open Source Project and I=92m looking for a good starting point. >> >> Many Thanks in advance >> eactor >> >> > > --047d7b86f2a2f6bd1304dfaa3bb8 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
I'm afraid I don't know anything about it the= n. I doubt it's in Guile now.

Best,
Noah


On Fri, Jun 21, 20= 13 at 2:13 AM, <eactors@aol.com> wrote:
QT= stands for QuickThreads, and in some cases is a massive speed improvement. There was a technical paper on this back in the 94 called &quo= t;Tools and Techniques for Building Fast Portable Thread Packages".
On= an x86-architecture this speeds up SystemC by a factor of 40 (Linux Ubuntu). And I believe it will increase the arm speed by at least 500% for = my use case. Since the content switch isn=92t that big for the arm having less registers to save compared to the x86.
So QT should always be considered if available, but somehow it seems to pas= s into oblivion.
Ch= eers
eactor


-----Original Message-----
From: Noah Lavine <noah.b.lavine@gmail.com>
To: eactors <eactor= s@aol.com>
Cc: 14672 <14= 672@debbugs.gnu.org>
Sent: Thu, Jun 20, 2013 11:25 pm
Subject: Re: bug#14672: QT port for ARM within guile
Hello,

Excuse my ignorance, but what is a "QT"? I can tell you'= re not referring to the widget toolkit.

Also, I believe Guile uses pthreads on most platforms, so if you'r= e running Linux on ARM (which is the common case on ARM nowadays, I think),= you should have threads. Unless you want userspace threads.

Best,
Noah


On Thu, Jun= 20, 2013 at 12:07 AM, <eactors@aol.com> wrote:
=
Hello,

Hope you can help me with this. Do you know what the status of this port was? Did it work? I would like to add a Q= T for ARM into the SystemC Open Source Project and I=92m looking for a good starting point.
=A0
Many Thanks in advance
eactor
=A0


--047d7b86f2a2f6bd1304dfaa3bb8--