From: Andreas Jaeger <aj@suse.de>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: bfd_read and bfd_write
Date: Wed, 05 Sep 2001 23:15:00 -0000 [thread overview]
Message-ID: <u88zfsc0as.fsf@gromit.moeb> (raw)
In-Reply-To: <20010906112244.C24712@bubble.sa.bigpond.net.au>
Alan Modra <amodra@bigpond.net.au> writes:
>> it also covers the k&r problem - you cant rely on a k&r compiler to
>> report parameter mismatches.
>
> That's the other part of my bfd patchset: Fixing all the -Wconversion
> errors that gcc reports. I've done 32 bit native, 32 -> 64 bit xcompiles,
> with 64 bit native and 64 -> 32 bit xcompiles yet to do. The last two
> cases should catch all the int/long mismatches, the first two catch
> int/long vs. bfd_vma/bfd_size_type etc. mismatches.
Have you done --enable-targets=all --enable-64-bit-bfd builds - and
fixed all those warnings? Wow! I'm looking forward to that patch.
In that case we should add -Wconversion to build_warnings.
thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-09-05 23:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 22:20 Alan Modra
2001-09-05 9:45 ` Andrew Cagney
2001-09-05 12:21 ` Richard Henderson
2001-09-05 17:26 ` Andrew Cagney
2001-09-05 18:52 ` Alan Modra
2001-09-05 20:03 ` Andrew Cagney
2001-09-06 10:33 ` Nick Clifton
2001-09-18 3:27 ` Alan Modra
2001-09-19 11:58 ` Andrew Cagney
2001-09-20 9:52 ` Andrew Cagney
2001-09-05 23:15 ` Andreas Jaeger [this message]
2001-09-06 0:01 ` Alan Modra
2001-09-05 20:13 ` Hans-Peter Nilsson
2001-09-05 20:30 ` Alan Modra
2001-09-08 22:42 ` Jim Blandy
2001-09-09 7:24 ` Hans-Peter Nilsson
2001-09-10 9:51 ` Ian Lance Taylor
2001-09-10 17:56 ` Hans-Peter Nilsson
2001-09-10 18:04 ` Ian Lance Taylor
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=u88zfsc0as.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=ac131313@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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