From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11918 invoked by alias); 16 Aug 2012 05:21:46 -0000 Received: (qmail 11898 invoked by uid 22791); 16 Aug 2012 05:21:45 -0000 X-SWARE-Spam-Status: No, hits=-5.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-yw0-f47.google.com (HELO mail-yw0-f47.google.com) (209.85.213.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Aug 2012 05:21:32 +0000 Received: by yhjj56 with SMTP id j56so2658483yhj.20 for ; Wed, 15 Aug 2012 22:21:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=xh/Ua8do7I4Ma9xwfUqYllteLIzxvFU4jT+5VIhQVys=; b=cY3w7m0efZaV2Ar+U6EtmIBtMLsDUiEq+L+cU/pDpV79ctS+TKku1Fjfam6Z40d6dY c5jconiltd+T0AmpU8W5T2xDlejIb5uB+mm/eausgNFydfptaKlEVRrFOTT+OYrAgSXZ ceuzoDghg+9iM7rrSPQiVxX/SSIbLiH8BB1fpDMtYEH2FpMASVF+lX5tK9gYvMm+G2/p wN62zKnGPd2kbsxacIUFEE9WZ2G6iAFDARNmMrEG4q1fELuq1SJXVS9H1DP6POON0lf5 puBwLlR8yClS++PopH0r85SXo02voHg3q+HyUr0BVH3HyUrq+833gnxWCMRjRB2ZYn4Q kQXA== Received: by 10.66.75.104 with SMTP id b8mr28948469paw.21.1345094491223; Wed, 15 Aug 2012 22:21:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.75.104 with SMTP id b8mr28948435paw.21.1345094490970; Wed, 15 Aug 2012 22:21:30 -0700 (PDT) Received: by 10.68.8.9 with HTTP; Wed, 15 Aug 2012 22:21:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 16 Aug 2012 11:36:00 -0000 Message-ID: Subject: Re: print gcc optimization log From: Ian Lance Taylor To: Xin Tong Cc: gcc-help@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true X-Gm-Message-State: ALoCoQkCM+JBhIvK9yXjg76slg5otMJ1RmRVi05aoMGw/v8mNUtvyac9VK/qcZB1S4loGAqz9f93C1Qh5DFxLoXxQOksdcEo1SwVnuVHcqElJmWxgEA6b6Bwb11XsnZ6ExJ4odGl+8XoV0EW6mrM0h0+BQS8FldKv2M3SpyxNgRDnD/h4gdkuYVM0unibtc+82kGqo/YudVj X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2012-08/txt/msg00120.txt.bz2 On Wed, Aug 15, 2012 at 8:58 PM, Xin Tong wrote: > I sometimes run into issues where i want to figure out why gcc is > performing a specific optimization and what the optimization affects > the tree. is there any documents on how to print gcc optimizations and > code generation logs ? Unfortunately GCC has very little in the way of logs intended for end users. About all I know is the -ftree-vectorizer-verbose information, which gives useful feedback about the vectorization optimizations. You can a lot of information by using -fdump-tree-all-details -fdump-rtl-all-details, but it's difficult to interpret without the source code and a working knowledge of GCC internals. Ian