public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "f4grx+bzsw at f4grx dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug sim/25211] sim: m68hc11: fails to remap registers when writing INIT Date: Wed, 09 Nov 2022 15:17:52 +0000 [thread overview] Message-ID: <bug-25211-4717-EJqnj8j4s7@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25211-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25211 --- Comment #5 from Sebastien F4GRX <f4grx+bzsw at f4grx dot net> --- Hello, I really appreciate that you managed to produce a minimal test case to reproduce the bug. I should have done that. TBH it's quite hard for me to contribute here because there are so many rules in places that I feel overwhelmed and dont know how to start. There is also a LOT of legacy in these complex code bases and even if I could hack something that worked, I have absolutely no idea how to fix this properly. Meanwhile, I have coded my own simulator where this function works. Setting init to zero is quite important in the 68hc11, because in extended mode, when you intend to use the hc11 as an almost generic microprocessor (not just with a small embedded task), then the default value of INIT means that the IO range lies in the middle of any large external ram you install on the bus. I am very grateful that you have identified the issue. I dont know how to fix it but I DEFINITELY volunteer to test it. Sebastien -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-09 15:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25211-4717@http.sourceware.org/bugzilla/> 2021-01-11 6:54 ` [Bug sim/25211] m68hc11 sim " vapier at gentoo dot org 2021-01-12 8:32 ` f4grx+bzsw at f4grx dot net 2021-10-31 17:27 ` [Bug sim/25211] sim: m68hc11: " vapier at gentoo dot org 2022-11-08 8:50 ` vapier at gentoo dot org 2022-11-09 14:50 ` vapier at gentoo dot org 2022-11-09 15:17 ` f4grx+bzsw at f4grx dot net [this message] 2022-11-10 15:05 ` vapier at gentoo dot org 2022-12-20 1:32 ` vapier at gentoo dot org 2023-01-12 15:41 ` f4grx+bzsw at f4grx dot net
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=bug-25211-4717-EJqnj8j4s7@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).