linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Yura Pakhuchiy <pakhuchiy@gmail.com>
Cc: Nathan Scott <nathans@sgi.com>,
	linux-xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, tibor@altlinux.ru,
	pakhuchiy@iptel.by
Subject: Re: XFS corruption on move from xscale to i686
Date: Thu, 14 Jul 2005 15:38:30 +0100	[thread overview]
Message-ID: <20050714143830.GA17842@infradead.org> (raw)
In-Reply-To: <60868aed050714065047e3aaec@mail.gmail.com>

On Thu, Jul 14, 2005 at 04:50:01PM +0300, Yura Pakhuchiy wrote:
> 2005/7/14, Nathan Scott <nathans@sgi.com>:
> > On Wed, Jul 13, 2005 at 06:22:28PM +0300, Yura Pakhuchiy wrote:
> > > I found patch by Greg Ungreger to fix this problem, but why it's still
> > > not in mainline? Or it's a gcc problem and should be fixed by gcc folks?
> > 
> > Yes, IIRC the patch was incorrect for other platforms, and it sure
> > looked like an arm-specific gcc problem (this was ages back, so
> > perhaps its fixed by now).
> 
> AFAIR gcc-3.4.3 was released after this conversation take place at linux-xfs,
> maybe add something like this:
> 
> #ifdef XSCALE
>     /* We need this because some gcc versions for xscale are broken. */
>     [patched version here]
> #else
>     [original version here]
> #endif

no, just fix your compiler or let the gcc folks do it.  Did anyone of
the arm folks ever open a PR at the gcc bugzilla with a reproduced
testcase?  You're never get your compiler fixed with that attitude.

  parent reply	other threads:[~2005-07-14 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 17:15 XFS corruption on move from xscale to i686 Yura Pakhuchiy
2005-07-08  4:21 ` Nathan Scott
2005-07-13 15:22   ` Yura Pakhuchiy
2005-07-14  1:20     ` Nathan Scott
2005-07-14 13:50       ` Yura Pakhuchiy
     [not found]       ` <60868aed050714065047e3aaec@mail.gmail.com>
2005-07-14 14:38         ` Christoph Hellwig [this message]
2005-07-14 14:45           ` Yura Pakhuchiy
2005-07-14 14:49             ` Christoph Hellwig

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=20050714143830.GA17842@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nathans@sgi.com \
    --cc=pakhuchiy@gmail.com \
    --cc=pakhuchiy@iptel.by \
    --cc=tibor@altlinux.ru \
    /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).