X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: Tatsuro MATSUOKA <matsuoka AT mol DOT nagoya-u DOT ac DOT jp>
To: cygwin AT cygwin DOT com
Cc: matsuoka AT nuce DOT nagoya-u DOT ac DOT jp
Date: Thu, 6 Sep 2007 10:25:54 +0900
Subject: Re: Slowness problem due to  sjlj-exceptions for Octave
Reply-To: matsuoka AT nuce DOT nagoya-u DOT ac DOT jp
In-Reply-To: <46DF4200.54D01692@dessent.net>
References: <20070906082343 DOT 87689790 DOT matsuoka AT mol DOT nagoya-u DOT ac DOT jp> <46DF4200 DOT 54D01692 AT dessent DOT net>
Message-Id: <20070906102554.CE896C00.matsuoka@mol.nagoya-u.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: nPOP Ver 1.0.9
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Thank you Brain
>Maybe I'm misremembering, but I thought that the current octave package
>maintainer entertained the idea of building the octave packages with a
>gcc that had been rebuilt with --disable-sjlj-exceptions.  I don't
>remember why this never happened.  At the very least, we had this same
>discussion about SJLJ when the octave packages were first introduced, or
>shortly thereafter.

James R. Phillips, who is a maintainer of octave 2.1.73. Pherhaps he 
is not working as a maintainer because he has not been made any 
respose when I threw a topic of  my testing binary of Octave 2.9.12 
on cygwin.

John W. Eaton, who is a main develper, seems not to like use 
undefault complier because octave uses the develop category tools 
including gcc for the advanced user tool. (Function can be complied 
to specially named dynamic link library *.oct)
He is afraid that the specially prepared complier confuses the user.

For this reason, James selected the gcc normally prepared.
At that time, there was no other way to build octave on windows so 
that even slow binary is meaningful.       

>But MSVCRT is part of the operating system and exists on every
>installation of Windows and needn't be distributed, so MinGW binaries
>are effectively stand-alone.  Users of MinGW have very different
>expectations than users of Cygwin, which is why for Cygwin we could very
>well just make shared libgcc/libstdc++/libgfortran (et al.) the default
>and not worry so much about supporting the static case, but that's not
>realistic for MinGW.

I understand what you would like to say.

>
>However this doesn't directly have anything to do with the Dwarf2/SJLJ
>issue; it is relevant only in the context of moving to gcc 4.x as the
>supported version.  (Of course, since 4.3 brings the possibility of
>doing away with SJLJ for good, I suppose it might be indirectly
>related.)

As an user's stand point, technical problem  of Dwarf2/SJLJ is not be 
concerned.
I would like to get good compliers in which the fast and safe 
exceptions facilities are worked. 

However I thank to the cygwin developers' efforts every day because 
the I'm using cygwin every day.

Thank to all contributers to the cygwin.

Sincerely,
Tatsuro MATSUOKA


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/