Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH] MIPS: Run checksyscalls for N32 and O32 ABI
Date: Sat, 12 May 2007 20:58:54 +0200	[thread overview]
Message-ID: <20070512185854.GA8647@uranus.ravnborg.org> (raw)
In-Reply-To: <20070513.014713.74753298.anemo@mba.ocn.ne.jp>

On Sun, May 13, 2007 at 01:47:13AM +0900, Atsushi Nemoto wrote:
> On Fri, 11 May 2007 21:23:55 +0200, "Franck Bui-Huu" <vagabon.xyz@gmail.com> wrote:
> > Well I'm not sure how revelant are the echos...
> 
> Without the echos, you can get something like this and it seems unlear
> which ABI should be fixed.
> 
>   CALL    /home/git/linux-mips/scripts/checksyscalls.sh
>   ...
>   CALL    /home/git/linux-mips/scripts/checksyscalls.sh
>   ...
>   CALL    /home/git/linux-mips/scripts/checksyscalls.sh
>   ...
> 
> > But I still think that (a) you shouldn't put any command in
> > 'archprepare' multiple rule (b) you should move this rule from the
> > cleaning targets.
> 
> Oh, I missed those points.  Revised again.
> 
> 
> Subject: [PATCH] MIPS: Simplify missing-syscalls for N32 and O32

This is overengineered. The only reason to make the syscall check
for each and every build was that this was easy and the missing syscalls
are easy to spot during a normal build.
But checking all combinations is just not worth it.
The arch responsible are assumed to build for the different architectures
once in a while so a missing syscall are likely to be detected anyway.

We cannot run each and every consistency check in all combinations
for each build - that would end in only build noise.

	Sam

  reply	other threads:[~2007-05-12 18:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 16:02 [PATCH] MIPS: Run checksyscalls for N32 and O32 ABI Atsushi Nemoto
2007-05-11 10:49 ` Ralf Baechle
2007-05-11 12:14 ` Franck Bui-Huu
2007-05-11 13:51   ` Thiemo Seufer
2007-05-11 14:41     ` Atsushi Nemoto
2007-05-11 15:59   ` Atsushi Nemoto
2007-05-11 19:23     ` Franck Bui-Huu
2007-05-12 16:47       ` Atsushi Nemoto
2007-05-12 18:58         ` Sam Ravnborg [this message]
2007-05-13 13:51           ` Atsushi Nemoto
2007-05-14  7:27           ` Franck Bui-Huu
2007-05-14  7:23         ` Franck Bui-Huu
2007-05-14  7:46           ` Atsushi Nemoto
2007-05-14  7:55             ` Franck Bui-Huu
2007-05-14  8:07               ` Atsushi Nemoto
2007-05-14 10:32                 ` Franck Bui-Huu
2007-05-14 10:42                   ` Franck Bui-Huu
2007-05-14 13:29                   ` Atsushi Nemoto
2007-05-29 15:38         ` Atsushi Nemoto
2007-05-31 12:14           ` Ralf Baechle

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=20070512185854.GA8647@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=vagabon.xyz@gmail.com \
    /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