From: lehmann@ans-netz.de (Oliver Lehmann)
Subject: [TUHS] Introduction
Date: Mon, 30 Jun 2008 19:34:50 +0200 [thread overview]
Message-ID: <20080630193450.b82063bb.lehmann@ans-netz.de> (raw)
In-Reply-To: <20080630113028.46a50360@veda.cnb.uam.es>
Jose R. Valverde wrote:
> But you would still be able to see what did generate the code (barring
> register number).
my C code:
register char *r2;
register long r4;
r2 = uap->linkname;
r4 = (long) r2;
r4 &= 0x7F00FFFF;
u.u_dirp.l = (caddr_t) r4;
leads to:
ldl rr2,rr8(#4) /* r2 = uap->linkname; */
ldl |_stkseg+~L1|(fp),rr2 /* r2 = uap->linkname; */
ldl |_stkseg+~L1+4|(fp),rr2 /* r4 = (long) r2; */
ldl rr4,rr2 /* r4 &= 0x7F00FFFF; */
and r4,#32512 /* r4 &= 0x7F00FFFF; */
ldl |_stkseg+~L1+4|(fp),rr4 /* r4 &= 0x7F00FFFF; */
ldl _u+78,rr4 /* u.u_dirp.l = (caddr_t) r4; */
looks not sooo bad - just the assigning into the stacked variables (no
idea why no register bound is used here even if I told the compiler to
make them register bound - but ,,register'' isn't that strong anyway)
> That is why I suggested the extra cast to
> see if the compiler would be misled into using an unneeded zero-offset
> assignment instruction to an auxiliary register.
>
> u.u_dirp.l = (caddr_t) ((long) (((saddr_t) uap->linkname).l) & 0x7F00FFFF);
> [...]
> but introducing a saddr_t cast that might fool the compiler into a
> temporary assignment with a zero offset (the .l) into ldl rr4,rr2
but not with that code :/
u.u_dirp.l = (caddr_t) ((long) (((saddr_t) uap->linkname).l) & 0x7F00FFFF);
"sys2_.c":50: operands of CAST have incompatible types
"sys2_.c":50: warning: struct/union or struct/union pointer required
Thats why I changed it the last time... to * and ->.
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
next prev parent reply other threads:[~2008-06-30 17:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 11:57 Jose R. Valverde
2008-06-04 15:11 ` Oliver Lehmann
2008-06-04 15:16 ` Oliver Lehmann
2008-06-05 15:07 ` Jose R. Valverde
2008-06-05 17:59 ` Oliver Lehmann
2008-06-05 15:17 ` Jose R. Valverde
2008-06-05 17:45 ` Oliver Lehmann
2008-06-23 14:18 ` Jose R. Valverde
2008-06-23 16:11 ` Oliver Lehmann
2008-06-25 9:40 ` Jose R. Valverde
2008-06-25 10:25 ` Jose R. Valverde
2008-06-26 14:52 ` Oliver Lehmann
2008-06-27 12:24 ` Jose R. Valverde
2008-06-29 8:25 ` Oliver Lehmann
2008-06-30 9:30 ` Jose R. Valverde
2008-06-30 17:34 ` Oliver Lehmann [this message]
2008-07-01 14:21 ` Jose R. Valverde
2008-07-01 18:35 ` Oliver Lehmann
2008-07-03 10:12 ` Jose R. Valverde
2008-07-06 16:14 ` Oliver Lehmann
2008-07-07 9:25 ` [TUHS] SysIII/PDP-11 on SIMH (was Re: Introduction) Jose R. Valverde
2008-07-07 9:32 ` [TUHS] Introduction Jose R. Valverde
2008-07-07 14:45 ` Oliver Lehmann
2008-06-06 9:58 ` Jose R. Valverde
-- strict thread matches above, loose matches on Subject: below --
2008-06-03 4:18 Oliver Lehmann
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=20080630193450.b82063bb.lehmann@ans-netz.de \
--to=lehmann@ans-netz.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;
as well as URLs for NNTP newsgroup(s).