From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) by sourceware.org (Postfix) with ESMTPS id 3F8C13954801 for ; Thu, 8 Apr 2021 20:23:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3F8C13954801 Received: by mail-qt1-x830.google.com with SMTP id f12so2502055qtf.2 for ; Thu, 08 Apr 2021 13:23:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FCFdx4XnRgy/06G+KHzjnzq8aiUtZ5PMQa5mf7bbN4o=; b=o8W37EXAnnmmwkPCw/sPHaiAp38xXL7du1U7VXvvJsn8ZEBkf4SUfb6B4Qjp/6Jikf 4gr3RKDxcVU0qYrJKxDi/yYDo39Z8hG7wZQGZ0aNrGYGQlpUcsMZDfB25lvEhoECoKNR ZQubA44Q0iNrdnQLqgG3sPMSb3uZ5UR5PTvd+LCHJ4Po6vr220WPt7dqfgM5m05UzZbc ZxOFL+mMjVEXAsOJms0vRi0K3d7LXvNZu0WP9MBdxCl7pyzA3ZBSn8TH+CLgRAaVuTja o5YESdz3hzyUrYPGOb12U/tfix04qINuXMvQ5vsD2Pq75Cl/IeB0bcltKQGpHcHOAJDe IaPg== X-Gm-Message-State: AOAM531R3oxQzodXLoIIb0OZf7iX29F8wx4Z7z587NEi4/1yexDyea3M P6W6YBYPq8Z+LO7vfC6u6J7vE8MEzdsgxQ== X-Google-Smtp-Source: ABdhPJxdKYIqUj9Ko22RTSn+/tBS0DMLJIJQmKRjLjxZX3Zh2/lUnqtJhTQIOqHDr7bvgTFGRPaSeg== X-Received: by 2002:ac8:1404:: with SMTP id k4mr8955260qtj.170.1617913409785; Thu, 08 Apr 2021 13:23:29 -0700 (PDT) Received: from ?IPv6:2804:7f0:4841:2841:5812:8068:979a:a62c? ([2804:7f0:4841:2841:5812:8068:979a:a62c]) by smtp.gmail.com with ESMTPSA id e2sm399795qto.50.2021.04.08.13.23.28 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 08 Apr 2021 13:23:29 -0700 (PDT) Subject: Re: [PATCH] [sim,rx] Silence warning that turns into a build error To: gdb-patches@sourceware.org References: <20210408195143.1349459-1-luis.machado@linaro.org> From: Luis Machado Message-ID: <07869142-e6ce-b480-56dc-334f2108e4b0@linaro.org> Date: Thu, 8 Apr 2021 17:23:27 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2021 20:23:31 -0000 On 4/8/21 5:16 PM, Mike Frysinger wrote: > On 08 Apr 2021 16:51, Luis Machado via Gdb-patches wrote: >> + FP_Parts a = {0, 0, 0, 0, 0}; > > wouldn't it be simpler & equiv: > FP_Parts a = {}; > -mike > I find that it works, but I'm unsure if it is a standard way of doing it. The C reference says: "When initializing an object of struct or union type, the initializer must be a non-empty, brace-enclosed, comma-separated list of initializers for the members." So I went with the most obvious, as opposed to going shorter and more opaque.