From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix frame ID comparison problem on s390
Date: Sun, 27 Jun 2004 21:48:00 -0000 [thread overview]
Message-ID: <20040627214831.GA30684@nevyn.them.org> (raw)
In-Reply-To: <200406272047.WAA10464@faui1m.informatik.uni-erlangen.de>
On Sun, Jun 27, 2004 at 10:47:58PM +0200, Ulrich Weigand wrote:
> Andrew Cagney wrote:
>
> > with those changes its ok,
>
> Thanks; here's the version I finally committed.
>
> (Sorry it took so long, I got sidetracked by a kernel bug triggered
> by running the gdb test suite that caused random kernel memory
> corruption :-/)
Thanks! Just one small nit. If you're going to do this:
> + id.stack_addr_p = 1;
> id.code_addr = code_addr;
> + id.code_addr_p = 1;
> id.special_addr = special_addr;
> + id.special_addr_p = 1;
Then these should be "unsigned int : 1":
> + /* Flags to indicate the above fields have valid contents. */
> + int stack_addr_p : 1;
> + int code_addr_p : 1;
> + int special_addr_p : 1;
> };
>
> /* Methods for constructing and comparing Frame IDs.
Some future version of GCC will warn about this mistake. The only
valid values for "int : 1" are 0 and -1.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-27 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 13:31 Ulrich Weigand
2004-05-20 14:17 ` Daniel Jacobowitz
2004-05-24 13:45 ` Ulrich Weigand
2004-05-24 18:52 ` Andrew Cagney
2004-06-09 14:12 ` Ulrich Weigand
2004-06-09 14:55 ` Andrew Cagney
2004-06-16 13:48 ` Ulrich Weigand
2004-06-16 17:33 ` Andrew Cagney
2004-06-27 20:48 ` Ulrich Weigand
2004-06-27 21:48 ` Daniel Jacobowitz [this message]
2004-06-27 22:35 ` Ulrich Weigand
2004-06-27 22:59 ` Andreas Schwab
2004-06-27 23:11 ` Daniel Jacobowitz
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=20040627214831.GA30684@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=weigand@i1.informatik.uni-erlangen.de \
/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