From: Eli Zaretskii <eliz@is.elta.co.il>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Should we fix warnings from GCC 2.xx?
Date: Thu, 19 Sep 2002 04:12:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020919130846.867E-100000@is> (raw)
In-Reply-To: <20020911234319.GN1105@gnat.com>
On Wed, 11 Sep 2002, Joel Brobecker wrote:
> > tracepoint.c: In function `trace_find_tracepoint_command':
> > tracepoint.c:2077: warning: suggest explicit braces to avoid ambiguous `else'
>
> This warning appears with a GCC 2.8.1-based compiler, but does not
> with GCC 3.0.4. Hence my question, do we want to fix these warnings
> anyway?
FWIW, I'm still using GCC 2.7.2.1 on one of my machines.
next prev parent reply other threads:[~2002-09-19 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 16:43 Joel Brobecker
2002-09-12 8:53 ` Andrew Cagney
2002-09-12 11:50 ` Joel Brobecker
2002-09-19 4:12 ` Eli Zaretskii [this message]
2002-09-19 4:31 ` Andreas Schwab
2002-09-19 4:49 ` Eli Zaretskii
2002-09-19 5:03 ` Andreas Schwab
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=Pine.SUN.3.91.1020919130846.867E-100000@is \
--to=eliz@is.elta.co.il \
--cc=brobecker@gnat.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