From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11112 invoked by alias); 13 May 2017 02:27:46 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 11051 invoked by uid 89); 13 May 2017 02:27:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy= X-HELO: mail-lf0-f43.google.com Received: from mail-lf0-f43.google.com (HELO mail-lf0-f43.google.com) (209.85.215.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 13 May 2017 02:27:42 +0000 Received: by mail-lf0-f43.google.com with SMTP id j1so9364070lfh.2 for ; Fri, 12 May 2017 19:27:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PRo454PqIYLohcVqPDJjybSL920LhxesCfxl4vMJbRQ=; b=BbmApthLFQNuScHzWWt6vmx7XL0ClMNg0Ler6T6YVRA1Izw5Lj8D72BezJCChX9jc4 7QI8OwQmuNy9mwlVnZaA6CyDzlVmspDiMKWeWzZFLl9OHCeB3mNXpTJjKglI/4Ifr4bY V+jytwJW4ssYe56kmH41vyYHyept5eiIa6DpMqqyy0+IrMvii3iWcKs1iAoBcSLEaGYH 8xyY/hXqxMjdnpmcc4rzM5y9c2qFuz/xK5jZaxMoAve1ziMB5l3tfdAyzq6CHnnsyVE2 CF4kixWuMhBoJGSxkPw1U/ttF1nYcIVXWLdTE/WZg/clc67SVUOsOh35Q3IT2WCVJtQm UIjw== X-Gm-Message-State: AODbwcBHAIySKhPobrC/EdO3v2JVUHOaQQVLgBbx5/Xpr6lcn+o482S4 Ec4AnMd4exSSqryqecprTvWvNioBPdZC X-Received: by 10.25.195.21 with SMTP id t21mr2525812lff.103.1494642463278; Fri, 12 May 2017 19:27:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.214.2 with HTTP; Fri, 12 May 2017 19:27:42 -0700 (PDT) In-Reply-To: <64e524ac-1a6a-44b2-dba7-9bfed5c0edf4@gmail.com> References: <64e524ac-1a6a-44b2-dba7-9bfed5c0edf4@gmail.com> From: Jim Wilson Date: Sat, 13 May 2017 06:16:00 -0000 Message-ID: Subject: Re: [PATCH] handling address mode changes inside extract_bit_field To: Martin Sebor Cc: Jeff Law , "gcc-patches@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2017-05/txt/msg01084.txt.bz2 On Fri, May 12, 2017 at 7:01 PM, Martin Sebor wrote: > Explicitly passing the additional argument at all the call sites > can be mitigated by giving the new alt_rtl argument a default > value of NULL in the declarations of the extract_bit_field functions. I keep forgetting about C++ features, as I'm not used to writing C++. I already checked in the patch, and I don't see the benefit of changing it again. I will try to remember this for next time. Jim