From: "Stephen P. Becker" <geoman@gentoo.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
Dominic Sweetman <dom@mips.com>,
linux-mips@linux-mips.org, ralf@linux-mips.org,
Nigel Stephens <nigel@mips.com>, David Ung <davidu@mips.com>
Subject: Re: [PATCH] Improve atomic.h implementation robustness
Date: Thu, 02 Dec 2004 06:57:27 -0500 [thread overview]
Message-ID: <41AF0327.4060303@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58L.0412021151100.11480@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Thu, 2 Dec 2004, Stephen P. Becker wrote:
>
>
>>For what it's worth, I'm running 64-bit kernels on my O2 and Indy that
>>were compiled with gcc 3.4.3, and I have had no problems.
>
>
> Have you used CONFIG_BUILD_ELF64 or not? The former obviously works for
> me; it's the latter that may cause troubles.
>
> Maciej
I have used CONFIG_BUILD_ELF64 for an O2 kernel that booted, but
typically I just use the -mabi=o64 hack.
Steve
prev parent reply other threads:[~2004-12-02 11:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 7:00 [PATCH] Improve atomic.h implementation robustness Thiemo Seufer
2004-12-01 10:20 ` Dominic Sweetman
2004-12-01 10:20 ` Dominic Sweetman
2004-12-01 12:33 ` Ralf Baechle
2004-12-01 21:50 ` Maciej W. Rozycki
2004-12-01 23:39 ` Ralf Baechle
2004-12-02 0:01 ` Maciej W. Rozycki
2004-12-07 11:56 ` Richard Sandiford
2004-12-07 12:56 ` Thiemo Seufer
2004-12-07 19:28 ` Richard Sandiford
2004-12-08 0:09 ` Thiemo Seufer
2004-12-01 20:45 ` Thiemo Seufer
2004-12-01 21:53 ` Maciej W. Rozycki
2004-12-01 23:03 ` Thiemo Seufer
2004-12-02 0:17 ` Maciej W. Rozycki
2004-12-02 1:02 ` Thiemo Seufer
2004-12-02 8:01 ` Dominic Sweetman
2004-12-02 8:38 ` Thiemo Seufer
2004-12-02 11:31 ` Stephen P. Becker
2004-12-02 11:54 ` Maciej W. Rozycki
2004-12-02 11:57 ` Stephen P. Becker [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=41AF0327.4060303@gentoo.org \
--to=geoman@gentoo.org \
--cc=davidu@mips.com \
--cc=dom@mips.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.com \
--cc=ralf@linux-mips.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