From: Stan Shebs <shebs@cygnus.com>
To: scottb@netwinder.org
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Merge of ARM Linux port with existing ARM code...
Date: Thu, 16 Dec 1999 14:49:00 -0000 [thread overview]
Message-ID: <199912162249.OAA10157@andros.cygnus.com> (raw)
In-Reply-To: <3857DC13.438069C4@netwinder.org>
Date: Wed, 15 Dec 1999 13:21:07 -0500
From: Scott Bambrough <scottb@netwinder.org>
> That's a great start in the right direction. We can always come back
> and polish the code later on. I'll get the basic stuff in, then you
> can check it over in the next snap and tell me what I missed.
It doesn't seem to be in this weeks snapshot, will it be in next weeks?
Just to confirm, I've pasted in your ARM GNU/Linux changes. They're
not put in verbatim; I tweaked some names and usages to conform better
to the coding standards, and didn't apply some changes that only
rearranged code, so as to simplify the diffs. I didn't (intentionally
anyway :-) ) discard anything substantive, so you should get the next
snap and try patching in any changes you may have made since the
beginning of November. I also wrote ChangeLog entry and NEWS item.
Since I don't have a native to test on, the ARM GNU/Linux config
testing is up to you; but your tweaks in inferior function call code
results in four more passes in the testsuite, and no additional fails.
So thanks again for the contribution, and let me know how it all works
on the Netwinder!
Stan
From taylor@cygnus.com Fri Dec 17 16:02:00 1999
From: David Taylor <taylor@cygnus.com>
To: Jimmy Guo <guo@cup.hp.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: (patch) hpjyg03: (buildsym|language).[ch]
Date: Fri, 17 Dec 1999 16:02:00 -0000
Message-id: <199912172347.SAA29264@texas.cygnus.com>
X-SW-Source: 1999-q4/msg00405.html
Content-length: 1385
It has been noticed that the language.c portion of this patch causes
additional noise at startup. Namely:
warning: Unrecognized range check setting: "auto; currently off"
I'm curious as to whether this message gets printed at HP (or are
there other language.c patches not yet submitted that get rid of it).
In any case, here's a patch to eliminate that noise:
taylor@texas 548: cvs diff -c language.c
Index: language.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/language.c,v
retrieving revision 2.68
diff -c -r2.68 language.c
*** language.c 1999/12/13 18:00:13 2.68
--- language.c 1999/12/17 23:26:48
***************
*** 1578,1589 ****
add_language (&auto_language_defn);
language = savestring ("auto", strlen ("auto"));
- range = savestring ("auto", strlen ("auto"));
- type = savestring ("auto", strlen ("auto"));
-
- /* Have the above take effect */
-
set_language_command (language, 0);
set_type_command (NULL, 0);
set_range_command (NULL, 0);
}
--- 1578,1588 ----
add_language (&auto_language_defn);
language = savestring ("auto", strlen ("auto"));
set_language_command (language, 0);
+
+ type = savestring ("auto", strlen ("auto"));
set_type_command (NULL, 0);
+
+ range = savestring ("auto", strlen ("auto"));
set_range_command (NULL, 0);
}
From guo@cup.hp.com Fri Dec 17 17:03:00 1999
From: Jimmy Guo <guo@cup.hp.com>
To: David Taylor <taylor@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: (patch) hpjyg03: (buildsym|language).[ch]
Date: Fri, 17 Dec 1999 17:03:00 -0000
Message-id: <Pine.LNX.4.10.9912171658310.8681-100000@hpcll168.cup.hp.com>
References: <199912172347.SAA29264@texas.cygnus.com>
X-SW-Source: 1999-q4/msg00406.html
Content-length: 1597
Oops.
Yes what was submitted in this patch wasn't the complete thing -- the
language.c changes in the hpjyg20 patch fixes this problem.
- Jimmy Guo, guo@cup.hp.com
>It has been noticed that the language.c portion of this patch causes
>additional noise at startup. Namely:
>
> warning: Unrecognized range check setting: "auto; currently off"
>
>I'm curious as to whether this message gets printed at HP (or are
>there other language.c patches not yet submitted that get rid of it).
>
>In any case, here's a patch to eliminate that noise:
>
>taylor@texas 548: cvs diff -c language.c
>Index: language.c
>===================================================================
>RCS file: /cvs/cvsfiles/devo/gdb/language.c,v
>retrieving revision 2.68
>diff -c -r2.68 language.c
>*** language.c 1999/12/13 18:00:13 2.68
>--- language.c 1999/12/17 23:26:48
>***************
>*** 1578,1589 ****
> add_language (&auto_language_defn);
>
> language = savestring ("auto", strlen ("auto"));
>- range = savestring ("auto", strlen ("auto"));
>- type = savestring ("auto", strlen ("auto"));
>-
>- /* Have the above take effect */
>-
> set_language_command (language, 0);
> set_type_command (NULL, 0);
> set_range_command (NULL, 0);
> }
>--- 1578,1588 ----
> add_language (&auto_language_defn);
>
> language = savestring ("auto", strlen ("auto"));
> set_language_command (language, 0);
>+
>+ type = savestring ("auto", strlen ("auto"));
> set_type_command (NULL, 0);
>+
>+ range = savestring ("auto", strlen ("auto"));
> set_range_command (NULL, 0);
> }
next prev parent reply other threads:[~1999-12-16 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-03 12:02 Scott Bambrough
1999-12-10 16:49 ` Stan Shebs
1999-12-15 10:25 ` Scott Bambrough
[not found] ` <E11yJCG-0005dx-00@kings-cross.london.uk.eu.org>
1999-12-15 11:54 ` Scott Bambrough
1999-12-16 14:49 ` Stan Shebs [this message]
[not found] <199912152124.NAA07105@andros.cygnus.com>
1999-12-15 15:43 ` Scott Bambrough
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=199912162249.OAA10157@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=scottb@netwinder.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