From: John Wehle <john@feith.com>
To: sid@sources.redhat.com
Subject: sid-20110801 Patch to sync SYS_argc, SYS_argnlen, SYS_argn with newlib
Date: Mon, 19 Sep 2011 07:04:00 -0000 [thread overview]
Message-ID: <201109190703.p8J73b4m009321@jwlab.FEITH.COM> (raw)
Currently the default values used by sid for SYS_argc, SYS_argnlen, SYS_argn
don't match the default values used by newlib. Looking at the simulators
supplied with gdb we see they default to the same values as newlib. The
only exception is the gdb sh and sh64 simulators which use different values.
Given that the sid sh and sh64 simulators already provide a custom mapping
with matches the gdb simulators, it seems reasonible to sync the default
values used by sid with that values used by newlib and the gdb simulators.
This way new ports can just use the default newlib values and have command
line argument passing working "out of the box" with both the gdb simulators
and sid.
The enclosed patch has been tested on FreeBSD with sid configured for
tomi Borealis (a processor under development by Venray Technology).
ChangeLog:
Mon Sep 19 01:52:59 EDT 2011 John Wehle (john@feith.com)
* component/gloss/libgloss.h (SYS_argc, SYS_argnlen, SYS_argn):
Sync with newlib/libgloss/syscall.h.
-- John
------------------------8<------------------------------8<---------------
--- component/gloss/libgloss.h.ORIGINAL 2011-09-19 00:56:13.000000000 -0400
+++ component/gloss/libgloss.h 2011-09-18 03:00:01.000000000 -0400
@@ -39,9 +39,9 @@
SYS_gettimeofday = 19,
SYS_times = 20,
SYS_reconfig = 25,
- SYS_argc = 172,
- SYS_argnlen = 173,
- SYS_argn = 174,
+ SYS_argc = 22,
+ SYS_argnlen = 23,
+ SYS_argn = 24,
SYS_unsupported = 255 // arbitrary syscall number, unsupported by default gloss component
};
};
-------------------------------------------------------------------------
reply other threads:[~2011-09-19 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201109190703.p8J73b4m009321@jwlab.FEITH.COM \
--to=john@feith.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).