From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 14:37:54 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C3E137B401 for ; Mon, 14 Jul 2003 14:37:54 -0700 (PDT) Received: from pop015.verizon.net (pop015pub.verizon.net [206.46.170.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54DD643F3F for ; Mon, 14 Jul 2003 14:37:53 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by pop015.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030714213752.BJGP20810.pop015.verizon.net@mac.com> for ; Mon, 14 Jul 2003 16:37:52 -0500 Message-ID: <3F1322A9.8080805@mac.com> Date: Mon, 14 Jul 2003 17:37:45 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd Questions X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop015.verizon.net from [141.149.47.46] at Mon, 14 Jul 2003 16:37:52 -0500 Subject: buggy optimization levels... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 21:37:54 -0000 Hi, all-- The "known bugs" section of the GCC info documentation lists 5 issues; "man gcc" lists none. Can someone provide a test case for a bug involving "cc -O" versus "cc -O3" under FreeBSD 4-STABLE for the x86 architecture? What is the preferred solution? The Dragon book and other compiler references have a definition of safe versus unsafe "optimizations"; is the problem that -O3 enables something unsafe? Who is responsible (FreeBSD, GNU compiler team, others?) for changing the compiler defaults so that -Ox will not produce known-invalid results, for any x? -- -Chuck