From: Arjan van de Ven <arjanv@redhat.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'C' calling convention change.
Date: Wed, 06 Oct 2004 15:16:50 +0200 [thread overview]
Message-ID: <1097068610.2812.19.camel@laptop.fenrus.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410060816430.3420@chaos.analogic.com>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Wed, 2004-10-06 at 14:20, Richard B. Johnson wrote:
> The new Red Hat Fedora release uses the following gcc version:
>
> gcc (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
>
> I have many assembly-language routines that need to interface with
> 'C' code. The new 'C' compiler is doing something different than
> gcc 3.2, previously used.
I assume you're talking about userspace code here. Why are you bringing
that up on the kernel list?
The gcc list or even a fedora(-devel) list would be far more
appropriate.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-06 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 12:20 Richard B. Johnson
2004-10-06 13:16 ` Arjan van de Ven [this message]
2004-10-06 13:34 ` Richard B. Johnson
2004-10-06 13:37 ` Arjan van de Ven
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=1097068610.2812.19.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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®