From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 34540 invoked by alias); 17 Jan 2018 20:48:01 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 34499 invoked by uid 89); 17 Jan 2018 20:48:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 17 Jan 2018 20:47:59 +0000 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D77AC80F9F; Wed, 17 Jan 2018 20:47:52 +0000 (UTC) Received: from greed.delorie.com (ovpn-124-118.rdu2.redhat.com [10.10.124.118]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5444C78E63; Wed, 17 Jan 2018 20:47:51 +0000 (UTC) Received: from greed.delorie.com.redhat.com (localhost [127.0.0.1]) by greed.delorie.com (8.14.7/8.14.7) with ESMTP id w0HKlnTs029585; Wed, 17 Jan 2018 15:47:49 -0500 From: DJ Delorie To: Eli Zaretskii Cc: schwab@linux-m68k.org, gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org Subject: Re: Compilation warning in simple-object-xcoff.c In-Reply-To: <83tvvkwlyn.fsf@gnu.org> (message from Eli Zaretskii on Wed, 17 Jan 2018 17:20:48 +0200) Date: Wed, 17 Jan 2018 20:48:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-01/txt/msg00358.txt.bz2 Eli Zaretskii writes: > DJ, would the following semi-kludgey workaround be acceptable? It would be no worse than what we have now, if the only purpose is to avoid a warning. Ideally, we would check to see if we're discarding non-zero values from that offset, and not call the callback with known bogus data. I suppose the usefulness of that depends on how often you'll encounter 4Gb+ xcoff64 files on mingw32 ?