From: Chuck Ebbert <76306.1226@compuserve.com>
To: mariusn <mariusn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux portability bugs
Date: Sun, 10 Dec 2006 23:46:45 -0500 [thread overview]
Message-ID: <200612102347_MC3-1-D49B-AB99@compuserve.com> (raw)
In-Reply-To: <a2705a960612012239j697f2799t27bec643f33c9e12@mail.gmail.com>
On Fri, 1 Dec 2006 22:39:01 -0800, mariusn wrote:
> I am a graduate student at University of Washington, building a tool
> automatically discover portability bugs in system-level code written
> in C. My definition of "portability" is at the data layout level,
> accounting for differences in alignment, padding, and generally layout
> policies on various platforms. E.g., one might perform a pointer cast
> that only works as intended when doubles are 4-byte aligned, which is
> the case with gcc/ia-32 (default options) but not with gcc/sparc (due
> to sparc's limited support for accessing doubles on non-8-byte
> boundaries).
>
> I am looking for advice on how/where to look for these kinds of bugs
> in the kernel and related software. This (dated) document
> (http://netwinder.osuosl.org/users/b/brianbr/public_html/alignment.html
> ) describes exactly these sorts of issues in the context of Linux/ARM
> and mentions things like the kernel, binutils, cpio, X11, Orbit, as
> sources of these sorts of bugs. I am having a bit of a hard time
> locating change logs and otherwise related information on where these
> bugs occurred, patches that addressed them, etc.
Look for "compat" in the patch title and comments, like this one:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=46c5ea3c9ae7fbc6e52a13c92e59d4fc7f4ca80a
--
Chuck
"Even supernovas have their duller moments."
next reply other threads:[~2006-12-11 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 4:46 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-02 6:39 mariusn
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=200612102347_MC3-1-D49B-AB99@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mariusn@gmail.com \
/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
all inboxes | Powered by JetHome®