From: Nick Clifton <nickc@cambridge.redhat.com>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: ARM simulator coredump
Date: Thu, 10 Jan 2002 03:28:00 -0000 [thread overview]
Message-ID: <m3n0zma1sm.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <3C3CD2BA.30209@cygnus.com>
Hi Fred,
> The ARM simulator is dumping core during gdb testing for arm-elf:
Which gdb test(s) in particular ?
> This patch seems to work, but I've not really checked it too
> carefully for correctness. Can whomever is responsible for the ARM
> simulator look it over please? Thanks.
Sure - that would be me. The patch has the right idea, but also a few
mistakes. Mind you seeing it prompted me to dig up an old patch that
I had for this and apply it. Please try updating your sources and let
me know if this had fixed things.
In case you are interested here are a few comments on the patch.
> - if (cp14r0 && ARMul_CP14_R0_ENABLE)
> + if (ok && ARMul_CP14_R0_ENABLE)
This was a bug in the original code. The intention was to test the
ARMul_CP14_R0_ENABLE bit in the r0 register of co-processor 14, so '&'
should have been used instead of '&&'. Hence the correct version of
this line would be:
if (ok && (cp14r0 & ARMul_CP14_R0_ENABLE))
> - if (cp14r0 && ARMul_CP14_R0_CCD)
> + if (ok && ARMul_CP14_R0_CCD)
A similar comment applied here, plus there is no need to retest 'ok'.
> - if (state->CPRead[13] (state, 8, 0)
> + ARMword temp;
> + if (state->CPRead[13] (state, 8, &temp)
> && ARMul_CP13_R8_PMUS)
And here.
> + {
> + ARMword temp;
There is no need to declare a 'temp' variable here. There is a
variable of the same type and name declared at the top of the
function, and it is no longer being used by this point.
Cheers
Nick
next prev parent reply other threads:[~2002-01-10 11:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 15:00 Fred Fish
2002-01-09 15:31 ` Andrew Cagney
2002-01-10 3:28 ` Nick Clifton [this message]
2002-01-10 7:15 ` Andrew Cagney
2002-01-10 8:13 ` Nick Clifton
2002-01-10 3:29 ` ARM simulator maintainer Nick Clifton
2002-01-10 7:19 ` Andrew Cagney
2002-01-10 8:11 ` Nick Clifton
2002-01-10 8:31 ` Frank Ch. Eigler
2002-01-10 16:29 ` Andrew Cagney
2002-01-10 17:22 ` Frank Ch. Eigler
2002-01-10 17:34 ` Andrew Cagney
2002-01-10 17:53 ` Frank Ch. Eigler
2002-01-10 18:08 ` Andrew Cagney
2002-01-11 10:31 ` Frank Ch. Eigler
2002-01-11 11:06 ` Andrew Cagney
2002-01-10 7:33 ` RFC: ARM simulator coredump Richard Earnshaw
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=m3n0zma1sm.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@cambridge.redhat.com \
--cc=fnf@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