From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20906 invoked by alias); 19 Jun 2008 21:26:43 -0000 Received: (qmail 20898 invoked by uid 22791); 19 Jun 2008 21:26:43 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.246) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 19 Jun 2008 21:26:21 +0000 Received: by rv-out-0708.google.com with SMTP id c5so6357149rvf.56 for ; Thu, 19 Jun 2008 14:26:19 -0700 (PDT) Received: by 10.140.125.1 with SMTP id x1mr6974996rvc.287.1213910779457; Thu, 19 Jun 2008 14:26:19 -0700 (PDT) Received: by 10.140.161.12 with HTTP; Thu, 19 Jun 2008 14:26:19 -0700 (PDT) Message-ID: Date: Thu, 19 Jun 2008 21:26:00 -0000 From: "Andrew Pinski" To: "GCC List" Subject: [Tuples] Creating a GIMPLE_MODIFY_STMT unnecessary for gimplify_omp_for MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2008-06/txt/msg00466.txt.bz2 Hi, When I was comparing the tuples branch to the trunk, I noticed that inside gimplify_omp_for, we call build_gimple_modify_stmt and then fall through to GIMPLE_MODIFY_STMT but really we don't need it. I have not tested removing it but I thought I would send out what I found while reviewing gimplify.c. Thanks, Andrew Pinski