From: "kernel panic" <cinap_lenrek@gmx.de>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] 5l bug
Date: Tue, 30 Apr 2013 12:58:11 +0200 [thread overview]
Message-ID: <trinity-aad9b2de-58c9-4c88-9746-6b2c6c6fcb68-1367319491628@3capp-gmx-bs06> (raw)
In-Reply-To: <75f6e109-06a7-4435-9ca9-bfbe02771e09@googlegroups.com>
i is not ovious to me why that would work without adding a conditiona branch.
maybe my assumptions are wrong. can you show the resulting assembly for the
testcase?
> Gesendet: Dienstag, 30. April 2013 um 11:07 Uhr
> Von: zephyr.pellerin@gmail.com
> An: 9fans@9fans.net
> Betreff: Re: [9fans] 5l bug
>
> Patching p -> scond = q -> scond in /sys/src/cmd/5l/noop.c fixes this unfortunate linker bug.
>
--
cinap
prev parent reply other threads:[~2013-04-30 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 5:54 Paul Patience
2013-04-29 18:53 ` cinap_lenrek
2013-04-29 18:57 ` erik quanstrom
2013-04-29 19:06 ` cinap_lenrek
2013-04-29 19:08 ` erik quanstrom
2013-04-29 19:34 ` Richard Miller
2013-04-30 10:15 ` kernel panic
2013-04-30 9:07 ` zephyr.pellerin
2013-04-30 10:58 ` kernel panic [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=trinity-aad9b2de-58c9-4c88-9746-6b2c6c6fcb68-1367319491628@3capp-gmx-bs06 \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/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).