From: Arnd Bergmann <arnd@arndb.de>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, pavel@ucw.cz
Subject: Re: [PATCH] alternative compat_ioctl table implementation
Date: Fri, 2 May 2003 23:42:04 +0200 [thread overview]
Message-ID: <200305022342.05365.arnd@arndb.de> (raw)
In-Reply-To: <p73r87h1aq6.fsf@oldwotan.suse.de>
On Friday 02 May 2003 20:09, Andi Kleen wrote:
> Rather ugly. In my experience all vmlinux.lds hacks are very fragile
> and they break when you just look at them in the wrong way. Also when
> something goes wrong they are a bitch to debug. And binutils is not
> exactly known for not introducing bugs with new releases.
Ok.
> Can't you work around that gcc 2.95 bug in some other way ?
Yes. I noticed now that only the x86_64 code (from which I copied)
contains the assembly version that breaks on cross-compile
and the sparc64 version works fine.
Arnd <><
next prev parent reply other threads:[~2003-05-02 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200305021959.02726.arnd@arndb.de.suse.lists.linux.kernel>
2003-05-02 18:09 ` [PATCH] alternative compat_ioctl table implementation Andi Kleen
2003-05-02 21:42 ` Arnd Bergmann [this message]
2003-05-02 17:59 Arnd Bergmann
2003-05-02 18:09 ` Ben Collins
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=200305022342.05365.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).