public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] AVR32: Fix invalid constraints for stcond
Date: Tue, 11 Jul 2006 11:07:09 -0700	[thread overview]
Message-ID: <44B3E8CD.8070409@zytor.com> (raw)
In-Reply-To: <11526218024091-git-send-email-hskinnemoen@atmel.com>

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.

	-hpa

  parent reply	other threads:[~2006-07-11 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 12:43 [PATCH 0/7] AVR32 update Haavard Skinnemoen
2006-07-11 12:43 ` [PATCH 1/7] AVR32: CONFIG_DEBUG_BUGVERBOSE and CONFIG_FRAME_POINTER Haavard Skinnemoen
2006-07-11 12:43   ` [PATCH 2/7] AVR32: Fix invalid constraints for stcond Haavard Skinnemoen
2006-07-11 12:43     ` [PATCH 3/7] AVR32: Add support for irq-flags state tracing Haavard Skinnemoen
2006-07-11 12:43       ` [PATCH 4/7] AVR32: Turn off support for DISCONTIGMEM and SPARSEMEM Haavard Skinnemoen
2006-07-11 12:43         ` [PATCH 5/7] AVR32: Always enable CONFIG_EMBEDDED Haavard Skinnemoen
2006-07-11 12:43           ` [PATCH 6/7] AVR32: Export the find_*_bit() functions Haavard Skinnemoen
2006-07-11 12:43             ` [PATCH 7/7] AVR32: Add defconfig for AT32STK1002 Haavard Skinnemoen
2006-07-11 18:07     ` H. Peter Anvin [this message]
2006-07-11 19:26       ` [PATCH 2/7] AVR32: Fix invalid constraints for stcond Haavard Skinnemoen

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=44B3E8CD.8070409@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@osdl.org \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.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