public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: Compilation warning in simple-object-xcoff.c
Date: Tue, 16 Jan 2018 18:25:00 -0000	[thread overview]
Message-ID: <831sipy83q.fsf@gnu.org> (raw)
In-Reply-To: <xnpo69wunj.fsf@greed.delorie.com> (message from DJ Delorie on	Tue, 16 Jan 2018 13:00:48 -0500)

> From: DJ Delorie <dj@redhat.com>
> Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
> Date: Tue, 16 Jan 2018 13:00:48 -0500
> 
> 
> I think that warning is valid - the host has a 32-bit limit to file
> sizes (off_t) but it's trying to read a 64-bit offset (in that clause).
> It's warning you that you won't be able to handle files as large as the
> field implies.

If 32-bit off_t cannot handle this, then perhaps this file (or that
function) should not be compiled for a 32-bit host?

  reply	other threads:[~2018-01-16 18:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 17:45 Eli Zaretskii
2018-01-16 18:01 ` DJ Delorie
2018-01-16 18:25   ` Eli Zaretskii [this message]
2018-01-16 18:38     ` DJ Delorie
2018-01-16 22:01       ` Andreas Schwab
2018-01-17 15:21         ` Eli Zaretskii
2018-01-17 20:48           ` DJ Delorie
2018-01-18  3:25             ` Eli Zaretskii
2018-01-20 12:48               ` Eli Zaretskii
2018-01-21  5:01                 ` Ian Lance Taylor via gdb-patches
2018-01-21 15:45                   ` Eli Zaretskii
2018-01-22  4:27                     ` Joel Brobecker
2018-01-27 16:43                       ` Eli Zaretskii
2018-01-21 15:45                   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=831sipy83q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).