All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Samuel Rydh <samuel@ibrium.se>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: asm inline
Date: 29 Nov 2002 17:30:52 +0100	[thread overview]
Message-ID: <1038587452.4040.22.camel@zion> (raw)
In-Reply-To: <20021129160826.GA27950@ibrium.se>


On Fri, 2002-11-29 at 17:08, Samuel Rydh wrote:
>
> I just noticed that gcc 3.1 doesn't like the following:

According to Franz Sirl, gcc 3.2.1 is one of the very first gcc's
to not need any special patch for known bugs for PPC32 :) I'd
suggest you try this one.

I couldn't reproduce that bug with debian sid's gcc 2.95.4, 3.0.4 and
3.2.1

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-11-29 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 16:08 asm inline Samuel Rydh
2002-11-29 16:21 ` Gabriel Paubert
2002-11-29 17:49   ` Samuel Rydh
2002-12-02 11:17     ` Franz Sirl
2002-12-02 13:11       ` Samuel Rydh
2002-12-02 13:35         ` Andreas Schwab
2002-12-02 14:14           ` Kevin B. Hendricks
2002-12-02 14:29             ` Andreas Schwab
2002-12-02 14:37               ` Kevin B. Hendricks
2002-12-02 14:51                 ` Franz Sirl
2002-12-02 15:08                   ` Kevin B. Hendricks
2002-12-02 15:11                   ` Kevin B. Hendricks
2002-12-02 15:35                     ` Franz Sirl
2002-12-02 15:45                       ` Kevin B. Hendricks
2002-12-02 15:12         ` Franz Sirl
2002-12-02 17:00           ` Samuel Rydh
2002-12-02 17:53             ` Gabriel Paubert
2002-12-02 19:17               ` Samuel Rydh
2002-11-29 16:30 ` Benjamin Herrenschmidt [this message]
2002-12-02 14:29   ` Gabriel Paubert

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=1038587452.4040.22.camel@zion \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=samuel@ibrium.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.