From: Fernando Nasser <fnasser@redhat.com>
To: gdb-patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA]: testsuite/gdb.base/miscexprs.*
Date: Wed, 31 Oct 2001 12:27:00 -0000 [thread overview]
Message-ID: <3BE05E88.21E51F02@redhat.com> (raw)
In-Reply-To: <20011031175346.G32706@cygbert.vinschen.de>
Corinna Vinschen wrote:
>
> Hi,
>
> on my target I have the same problem with the very small (2K) stack
> when running miscexprs.exp as I already had with call-ar-st.exp.
>
> I would like to propose the following patch, which adds the ability
> to extend miscexprs.exp for targets, which also suffer from the
> small stack. I added a compiler switch to define the preprocessor
> symbol `STORAGE', which by default is set to empty. A target
> specific conditional can be used for setting it to "static", to
> allow running the tests with the datastructures allocated in the
> global data area instead of on the stack.
Hmm, I would have just set a, lets say, 'flag' variable and added
it to the gdb_compile statement "additional_flags= $flag -w"
(see long_long.exp). But don't bother, some other places even
forgot the -w.
> Obviously, miscexprs.exp
> in the below incarantion just contains such a conditional only for
> the target I'm just working on...
>
Well, this one gets me a little bit more concerned. It is very possible
that other targets have the same problem as yours. And, most important
of all, this is more of a board limitation than an architecture (which
is what the target triple defines) limitation. Or isn't it possible
that someone uses this chip to create a board with a larger stack
memory?
In this cases, we create an entry in the board info and set it (in the
boards file) with
set_board_info gdb,smallstack 1;
And test it (in the tests file) with
if [target_info exists gdb,smallstack] {
> Corinna
>
> 2001-10-31 Corinna Vinschen <vinschen@redhat.com>
>
> * gdb.base/miscexprs.c (main): Add usage of preprocessor
> symbol `STORAGE' to allow to choose the storage class of
> the local datastructures.
> * gdb.base/miscexprs.exp: Handle setting a `-DSTORAGE=...'
> compiler directive.
>
> Index: miscexprs.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/miscexprs.c,v
> retrieving revision 1.1.1.2
> diff -u -p -r1.1.1.2 miscexprs.c
> --- miscexprs.c 1999/04/26 18:27:11 1.1.1.2
> +++ miscexprs.c 2001/10/31 16:43:01
> @@ -7,27 +7,27 @@ marker1 ()
> int
> main ()
> {
> - struct {
> + STORAGE struct {
> char c[100];
> } cbig;
>
> - struct {
> + STORAGE struct {
> int i[800];
> } ibig;
>
> - struct {
> + STORAGE struct {
> long l[900];
> } lbig;
>
> - struct {
> + STORAGE struct {
> float f[200];
> } fbig;
>
> - struct {
> + STORAGE struct {
> double d[300];
> } dbig;
>
> - struct {
> + STORAGE struct {
> short s[400];
> } sbig;
>
> Index: miscexprs.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/miscexprs.exp,v
> retrieving revision 1.5
> diff -u -p -r1.5 miscexprs.exp
> --- miscexprs.exp 2001/03/06 08:21:50 1.5
> +++ miscexprs.exp 2001/10/31 16:43:01
> @@ -30,6 +30,17 @@ if $tracelevel then {
> strace $tracelevel
> }
>
> +# By default, the datastructures are allocated on the stack. For targets
> +# with very small stack, that will not work. In that case, just set
> +# storage to `-DSTORAGE=static' which changes the datastructures to be
> +# allocated in data segment.
> +set storage "-DSTORAGE="
> +if [istarget "stormy16-*-*"] then {
> + set storage "-DSTORAGE=static"
> +}
> +
> +set additional_flags "additional_flags=-w ${storage}"
> +
> #
> # test running programs
> #
> @@ -40,7 +51,7 @@ set testfile "miscexprs"
> set srcfile ${testfile}.c
> set binfile ${objdir}/${subdir}/${testfile}
>
> -if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug additional_flags=-w}] != "" } {
> +if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [list debug ${additional_flags}]] != "" } {
> gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
> }
>
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
prev parent reply other threads:[~2001-10-31 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 8:53 Corinna Vinschen
2001-10-31 11:39 ` Michael Snyder
2001-10-31 12:20 ` Corinna Vinschen
2001-10-31 12:33 ` Fernando Nasser
2001-10-31 13:00 ` Corinna Vinschen
2001-10-31 12:32 ` Fernando Nasser
2001-10-31 12:27 ` Fernando Nasser [this message]
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=3BE05E88.21E51F02@redhat.com \
--to=fnasser@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