Re: [PATCH 2/7] AVR32: Fix invalid constraints for stcond

[Haavard Skinnemoen]

On 7/11/06, H. Peter Anvin <hpa@xxxxxxxxx> wrote:
> Haavard Skinnemoen wrote:
> > Because gcc doesn't seem to like arch-dependent constraints in inline
> > asm, we ended up using "m" as constraint for the stcond instruction.
>
> Bunkum.  That would be a bug in the AVR32 gcc, but gcc handles
> arch-specific constraints in inline assembly all the time.  The kernel
> wouldn't compile for a large number of architectures otherwise.

Thanks, then we at least know it's a gcc bug. It's sometimes hard to
tell what features are actually supposed to work, especially the stuff
that's only documented in the internals manual...

Anyway, "o" is apparently more correct than "m" since with "o" it
manages to compile all the filesystems without complaining, and the
output looks correct. On the other hand, ocfs2 probably isn't
something you want to use on your AVR32 board...

Håvard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/