From: Newsgroups Reader <mail_lists@telus.net>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] JFFS2 on ARM target
Date: Wed, 08 Mar 2006 23:03:00 -0000 [thread overview]
Message-ID: <1141859007.8185.2.camel@saturn.dsivan.com> (raw)
In-Reply-To: <20060308215803.GD19406@lunn.ch>
We see the same behaviour with GCC for MIPS. The version is:
mipsisa32-elf-gcc (GCC) 3.2.1 (eCosCentric).
On Wed, 2006-03-08 at 22:58 +0100, Andrew Lunn wrote:
> On Wed, Mar 08, 2006 at 03:08:22PM -0500, Doyle, Patrick wrote:
> > I'm confused by something I'm seeing with JFFS2 on my arm target, and I was
> > wondering if anybody else had seen anything similar.
> >
> > Basically, what I see is that when JFFS2 goes through and marks a block as
> > being erased, it seems to me that it should be writing 'JFFS2_MAGIC_BITMASK'
> > (0x1985) to the marker for the block. What I'm seeing is that 0x2003 gets
> > written into the marker field.
> >
> > Staring at disassembled code for a couple of hours makes me believe that
> > this is, in fact, exactly what the opcodes are telling the CPU to do,
> > despite what one would expect from looking at the C code.
> >
> > So now I'm curious... are there known bugs with gcc 3.2.1 for the ARM that
> > make it a terrible candidate for processing linux-like code that includes
> > constructs such as:
> >
> >
> > struct jffs2_unknown_node marker = {
> > .magic = cpu_to_je16(JFFS2_MAGIC_BITMASK),
> > .nodetype = cpu_to_je16(JFFS2_NODETYPE_CLEANMARKER),
> > .totlen = cpu_to_je32(c->cleanmarker_size)
> > };
>
> packages/fs/jffs2/current/src/fs-ecos.c:24
>
> #if (__GNUC__ == 3) && (__GNUC_MINOR__ == 2) && defined (__ARM_ARCH_4__)
> #error This compiler is known to be broken. Please see:
> #error http://ecos.sourceware.org/ml/ecos-patches/2003-08/msg00006.html
> #endif
>
> 2003-09-23 Andrew Lunn <andrew.lunn@ascom.ch>
>
> * src/fs-ecos.c: Added test to detect known broken ARM compiler
>
> Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-03-08 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 20:00 Doyle, Patrick
2006-03-08 21:58 ` Andrew Lunn
2006-03-08 23:03 ` Newsgroups Reader [this message]
2006-03-09 16:18 Doyle, Patrick
2006-03-09 20:42 ` Andrew Lunn
2006-06-20 14:35 ` Jürgen Lambrecht
2006-03-09 20:11 Doyle, Patrick
2006-03-09 20:39 ` Andrew Lunn
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=1141859007.8185.2.camel@saturn.dsivan.com \
--to=mail_lists@telus.net \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).