From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26214 invoked by alias); 10 May 2009 22:00:44 -0000 Received: (qmail 25328 invoked by uid 48); 10 May 2009 22:00:31 -0000 Date: Sun, 10 May 2009 22:00:00 -0000 Message-ID: <20090510220031.25327.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/37179] gcc emits bad opcode 'ffreep' In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ubizjak at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-05/txt/msg00875.txt.bz2 ------- Comment #13 from ubizjak at gmail dot com 2009-05-10 22:00 ------- Created an attachment (id=17848) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17848&action=view) Patch This patch looks at processor name to detect AMD geode CPU. As far as gcc is concerned, "-march=geode" means AMD geode with 3dnow-a extensions. Other geodes are handled by generic processor detection, since we really have no better idea. Can someone please test attached patch with -march=native on geode? -- ubizjak at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |ubizjak at gmail dot com |dot org | Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37179