delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/11/20/14:10:15

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <3DDBDE09.4010906@freesurf.ch>
Date: Wed, 20 Nov 2002 20:10:01 +0100
From: Charles Werner <clw2 AT freesurf DOT ch>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: compile with -fomit-frame-pointer and gcc

I have the following to report, perhaps it is a bug in gcc for Cygwin.

I wrote a C subroutine that allocated 60000 integers on the stack each time it 
was called. Under Cygwin gcc 2.95x this worked fine. However, when compiled with 
the current gcc 3.2 it fails  if compiled  using the -fomit-frame-pointer 
optimization (default from configure).

Without this optimization turned on all is well. Declaring the array static 
cleared up this problem and the program can  be compiled and run sucessfully 
using -fomit-frame-pointer.

Cheers,
Charles Werner





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019