public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macq.eu>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Greg Ungerer <gerg@uclinux.org>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68k: use conventional function parameters for do_sigreturn
Date: Tue, 9 Feb 2016 16:26:03 +0100	[thread overview]
Message-ID: <20160209152603.GA31805@frolo.macqel> (raw)
In-Reply-To: <mvmh9hit0gx.fsf@hawking.suse.de>

On Tue, Feb 09, 2016 at 03:36:14PM +0100, Andreas Schwab wrote:
> Philippe De Muyter <phdm@macq.eu> writes:
> 
> > Given what gcc does now, how can scanf still work then ?
> 
> In which way is that related to scanf?

The scanf family uses/used varargs to determine the addresses of the
returned values to fill, like do_sigreturn.

But I see the difference now : with scanf only the addresses are on the
stack, while with do_sigreturn the values themselves are on the stack.

Philippe

-- 
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles

      reply	other threads:[~2016-02-09 15:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  5:56 [PATCH] m68k: use conventional function parameters for do_sigreturn Greg Ungerer
2016-02-01  4:33 ` Greg Ungerer
2016-02-01 18:39 ` Andreas Schwab
2016-02-01 23:59   ` Greg Ungerer
2016-02-02 19:25     ` Andreas Schwab
2016-02-03  4:14       ` Greg Ungerer
2016-02-08 23:31         ` Andreas Schwab
2016-02-09  0:21           ` Greg Ungerer
2016-02-09  9:48             ` Andreas Schwab
2016-02-09 13:05               ` Greg Ungerer
2016-02-09 13:17                 ` Andreas Schwab
2016-02-09 14:01                   ` Philippe De Muyter
2016-02-09 14:36                     ` Andreas Schwab
2016-02-09 15:26                       ` Philippe De Muyter [this message]

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=20160209152603.GA31805@frolo.macqel \
    --to=phdm@macq.eu \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@linux-m68k.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