From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH/committed 3/5] sim: m32r: fix missing break statement
Date: Wed, 10 Jan 2024 22:37:45 -0500 [thread overview]
Message-ID: <20240111033747.17795-3-vapier@gentoo.org> (raw)
In-Reply-To: <20240111033747.17795-1-vapier@gentoo.org>
The ftime syscall should not fallthrough to the sync syscall.
Clearly the code was missing a break statement.
---
sim/m32r/traps.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sim/m32r/traps.c b/sim/m32r/traps.c
index c5191989d7fd..9ffa3bb15d94 100644
--- a/sim/m32r/traps.c
+++ b/sim/m32r/traps.c
@@ -407,6 +407,7 @@ m32r_trap (SIM_CPU *current_cpu, PCADDR pc, int num)
errcode = EINVAL;
}
}
+ break;
case TARGET_LINUX_SYS_sync:
sync ();
--
2.43.0
next prev parent reply other threads:[~2024-01-11 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 3:37 [PATCH/committed 1/5] sim: m32r: cleanup unused variables Mike Frysinger
2024-01-11 3:37 ` [PATCH/committed 2/5] sim: m32r: migrate ftime() to clock_gettime() Mike Frysinger
2024-01-11 3:37 ` Mike Frysinger [this message]
2024-01-11 3:37 ` [PATCH/committed 4/5] sim: m32r: fixup some of the int<->pointer casts Mike Frysinger
2024-01-11 3:37 ` [PATCH/committed 5/5] sim: m32r: enable warnings in traps.c Mike Frysinger
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=20240111033747.17795-3-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).