From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12572 invoked by alias); 28 Sep 2002 23:00:55 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 12564 invoked from network); 28 Sep 2002 23:00:54 -0000 Received: from unknown (HELO mtvmime02.veritas.com) (143.127.3.10) by sources.redhat.com with SMTP; 28 Sep 2002 23:00:54 -0000 Received: from megami (unverified) by mtvmime02.veritas.com (Content Technologies SMTPRS 4.2.10) with SMTP id ; Sat, 28 Sep 2002 16:01:02 -0700 Received: from pacbell.net([172.22.12.210]) (941 bytes) by megami via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sat, 28 Sep 2002 16:00:54 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #15 built 2001-Aug-30) Message-ID: <3D9635BA.5DC3F94F@pacbell.net> Date: Sat, 28 Sep 2002 16:41:00 -0000 From: Bruce Korb Organization: Home X-Accept-Language: en MIME-Version: 1.0 To: gcc@gcc.gnu.org, Automake Development Subject: module level flags Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg01173.txt.bz2 As best as I can determine, there is no easy way to say, "do not optimize this particular module". The best way would be with a #pragma around the problematical function, but I'll be happy with anything that does not disable optimization for the entire program and does not prevent someone from overriding CFLAGS for that module, either. Suggestions? Thanks!