From: Elena Zannoni <elena.zannoni@oracle.com>
To: frysk <frysk@sourceware.org>
Subject: minutes 20070502
Date: Wed, 02 May 2007 16:08:00 -0000 [thread overview]
Message-ID: <4638AFD9.7050002@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 50 bytes --]
Sami, Rick: Please integrate with screenshots.
[-- Attachment #2: frysk-20070502 --]
[-- Type: text/plain, Size: 1264 bytes --]
Elena, Sami, Andrew, Rick, Stan, Nurdin
No vnc viewer, no visual.
Conversation btw Sami/Andrew hard to follow. Rick talked about source
window changes. Post new screenshots please.
Demo on IRC of the bitfields from Stan:
-----
flags.uc = 0xFF;flags.u1 = 0x1;flags.u2 = 0x3;flags.u3 = 0x7;flags.u9 = 0x1FF;
(fhpd) what flags
extern {byte uc;int s1;int u1;int s2;int u2;int s3;int u3;int s9;int u9;byte sc;} at /home/scox/accu/bugs/4228/4228.c#32
(fhpd) print flags
uc=-1,s1=1,u1=1,s2=1,u2=3,s3=1,u3=7,s9=1,u9=511,sc=1
-----
struct {class_t c1; class_t c2;} class_2 = {{1.0,1},{2.0,2}}; <-- source code
(fhpd) what class_2
{{double double_1;int int_1;} c1;{double double_1;int int_1;} c2;} at /home/scox/accu/src/hpd.c#160
(fhpd) print class_2
c1=double_1=1.0,int_1=1,c2=double_1=2.0,int_1=2
-----
class_t classes[] = {{1.0,1},{2.0,2},{3.0,3},{4.0,4}}; <-- source code
(fhpd) what classes
{double double_1;int int_1;} [3] at /home/scox/accu/src/hpd.c#159
(fhpd) print classes
{double_1=1.0,int_1=1,double_1=2.0,int_1=2,double_1=3.0,int_1=3,double_1=4.0,int_1=4}
----
struct {int arr [2][2];} class_3 = {{{1,2},{3,4}}}; <-- source code
(fhpd) what class_3
{int [2,2] arr;} at /home/scox/accu/src/hpd.c#161
(fhpd) print class_3
arr={{1,2},{3,4}}
next reply other threads:[~2007-05-02 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 16:08 Elena Zannoni [this message]
2007-05-02 16:34 ` Phil Muldoon
2007-05-03 13:52 ` Mike Cvet
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=4638AFD9.7050002@oracle.com \
--to=elena.zannoni@oracle.com \
--cc=frysk@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).