From: Elena Zannoni <ezannoni@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] fix warning in dwarfread.c
Date: Thu, 26 Jun 2003 22:31:00 -0000 [thread overview]
Message-ID: <16123.30184.642647.645807@localhost.redhat.com> (raw)
I got a warning using gcc 3.3.
elena
2003-06-26 Elena Zannoni <ezannoni@redhat.com>
* dwarfread.c (decode_modified_type): Gag new compiler warning.
Index: dwarfread.c
===================================================================
RCS file: /cvs/uberbaum/gdb/dwarfread.c,v
retrieving revision 1.28
diff -u -p -r1.28 dwarfread.c
--- dwarfread.c 23 Jun 2003 19:51:38 -0000 1.28
+++ dwarfread.c 26 Jun 2003 22:29:03 -0000
@@ -3198,8 +3198,12 @@ decode_modified_type (char *modifiers, u
DIE_ID, DIE_NAME); /* FIXME */
break;
default:
- if (!(MOD_lo_user <= (unsigned char) modifier
+ if (!(MOD_lo_user <= (unsigned char) modifier))
+#if 0
+/* This part of the test would always be true, and it triggers a compiler
+ warning. */
&& (unsigned char) modifier <= MOD_hi_user))
+#endif
{
complaint (&symfile_complaints,
"DIE @ 0x%x \"%s\", unknown type modifier %u", DIE_ID,
next reply other threads:[~2003-06-26 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 22:31 Elena Zannoni [this message]
2003-06-27 13:35 ` Elena Zannoni
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=16123.30184.642647.645807@localhost.redhat.com \
--to=ezannoni@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