From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6644 invoked by alias); 16 Oct 2006 18:28:31 -0000 Received: (qmail 6636 invoked by uid 22791); 16 Oct 2006 18:28:30 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Oct 2006 18:28:29 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id 57F7127B3C; Mon, 16 Oct 2006 11:28:28 -0700 (PDT) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16101-02; Mon, 16 Oct 2006 11:28:27 -0700 (PDT) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 4D23F27B6E; Mon, 16 Oct 2006 11:24:58 -0700 (PDT) Received: from 192.168.92.75 ([192.168.92.75]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Mon, 16 Oct 2006 18:24:58 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 16 Oct 2006 11:24:56 -0700 Subject: Re: [Off topic] GCC Control Flow Graphs From: Michael Snyder To: Rob Quill Cc: gdb@sourceware.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 16 Oct 2006 18:28:00 -0000 Message-Id: <1161023096.14535.337.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00118.txt.bz2 On Mon, 2006-10-16 at 14:35 +0100, Rob Quill wrote: > Hi, > > Does anyone know if it is possible to view/access/print out the > control flow graphs produced by GCC, either at compilation time, or > after compilation has taken place? This question might better be asked in the GCC mailing lists, but I think you can get way more information than you can possibly used by setting (eg.) gcc -save-temps.