mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: Sebastian Andrzej Siewior <bigeasy@breakpoint.cc>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] consider stack access while checking for alternate signal stack
Date: Mon, 19 Oct 2009 18:26:30 +0900	[thread overview]
Message-ID: <20091019182630.7c4fa4c1@hskinnemoen-d830> (raw)
In-Reply-To: <20091019075824.GA25783@Chamillionaire.breakpoint.cc>

Sebastian Andrzej Siewior <bigeasy@breakpoint.cc> wrote:
> >Sebastian Andrzej Siewior <sebastian@breakpoint.cc> wrote:  
> >> Haavard: The AVR32 assumption is pure on gcc's STACK_PUSH_CODE which is
> >> POST_DEC. Could you please ack/nak it?  
> >
> >Hmm, no, that is not correct. AVR32 is definitely pre-decrement.
> >
> >Note that 8-bit AVR and AVR32 are two completely different
> >architectures.  
> Ah okay. So the AVR32 bits are not in upstream GCC yet?

No, unfortunately not. We're working on it, and have been for some
time, but the progress is very slow.

Haavard

  reply	other threads:[~2009-10-19  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 19:12 Sebastian Andrzej Siewior
2009-10-19  4:09 ` Haavard Skinnemoen
2009-10-19  7:58   ` Sebastian Andrzej Siewior
2009-10-19  9:26     ` Haavard Skinnemoen [this message]
2009-10-19  7:33 ` Ingo Molnar
2009-10-19  8:02   ` Sebastian Andrzej Siewior
2009-10-19 18:08     ` Roland McGrath
2009-10-19 19:30       ` Sebastian Andrzej Siewior
2009-10-20 21:11         ` Roland McGrath
2009-10-21  8:28           ` Sebastian Andrzej Siewior
2009-10-25 14:37           ` [PATCH v2] consider the kind of stack incrementation " Sebastian Andrzej Siewior
2009-11-04 17:27             ` [tip:core/signal] signal: Fix alternate signal stack check tip-bot for Sebastian Andrzej Siewior

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=20091019182630.7c4fa4c1@hskinnemoen-d830 \
    --to=haavard.skinnemoen@atmel.com \
    --cc=bigeasy@breakpoint.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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
all inboxes | Powered by JetHome®