From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Geoff Keating <geoffk@redhat.com>
Cc: gcc-bugs@gcc.gnu.org, gdb-patches@sources.redhat.com
Subject: Re: 6 GCC regressions, 6 new, with your patch on 2002-01-29T19:24:37Z.
Date: Wed, 30 Jan 2002 12:16:00 -0000 [thread overview]
Message-ID: <20020130201849.GB11985@daikokuya.demon.co.uk> (raw)
In-Reply-To: <200201300518.g0U5ICY25065@desire.geoffk.org>
Geoff Keating wrote:-
> Hmmm. Actually, the first test, bitfields.exp, produces the warnings;
Hi Geoff,
This patch should fix the warnings. I'll turn my attention to the enum
issue once I've got rth's Alpha issue sorted (I've got some ideas about
that, but I'm just building a cross-compiler to try and reproduce the
situation).
I think this patch makes the tests do what they were supposed to do
previously, but without warnings. I'd appreciate if you or someone
with write access to GDB would apply it.
Thanks,
Neil.
* testsuite/gdb.base/bitfields.c: Correct assignments to
bitfields to avoid warnings.
Index: bitfields.c
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/bitfields.c,v
retrieving revision 1.1.1.2
diff -u -p -r1.1.1.2 bitfields.c
--- bitfields.c 1999/06/28 16:02:40 1.1.1.2
+++ bitfields.c 2002/01/30 20:10:35
@@ -80,7 +80,7 @@ int main ()
break1 ();
flags.uc = 0;
- flags.s1 = 1;
+ flags.s1 = -1;
break1 ();
flags.s1 = 0;
@@ -131,10 +131,10 @@ int main ()
flags.u3 = 0;
flags.u9 = 0;
- flags.s1 = 0x1;
- flags.s2 = 0x3;
- flags.s3 = 0x7;
- flags.s9 = 0x1FF;
+ flags.s1 = -1;
+ flags.s2 = -1;
+ flags.s3 = -1;
+ flags.s9 = -1;
flags.sc = 0xFF;
break2 ();
flags.s1 = 0;
@@ -169,20 +169,20 @@ int main ()
break4 ();
/* Maximally negative values */
- flags.s1 = 0x1;
- flags.s2 = 0x2;
- flags.s3 = 0x4;
- flags.s9 = 0x100;
+ flags.s1 = -0x1;
+ flags.s2 = -0x2;
+ flags.s3 = -0x4;
+ flags.s9 = -0x100;
/* Extract bitfield value so that bitfield.exp can check if the target
understands signed bitfields. */
i = flags.s9;
break4 ();
/* -1 */
- flags.s1 = 0x1;
- flags.s2 = 0x3;
- flags.s3 = 0x7;
- flags.s9 = 0x1FF;
+ flags.s1 = -1;
+ flags.s2 = -1;
+ flags.s3 = -1;
+ flags.s9 = -1;
break4 ();
flags.s1 = 0;
next parent reply other threads:[~2002-01-30 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201292158.g0TLw6f14961@maat.cygnus.com>
[not found] ` <20020129222235.GA4190@daikokuya.demon.co.uk>
[not found] ` <jmsn8ooi5w.fsf@desire.geoffk.org>
[not found] ` <20020129233808.GA4967@daikokuya.demon.co.uk>
[not found] ` <200201300518.g0U5ICY25065@desire.geoffk.org>
2002-01-30 12:16 ` Neil Booth [this message]
2002-01-30 14:27 ` Fernando Nasser
2002-01-30 14:39 ` Daniel Jacobowitz
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=20020130201849.GB11985@daikokuya.demon.co.uk \
--to=neil@daikokuya.demon.co.uk \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=geoffk@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