All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Franck Bui-Huu" <fbuihuu@gmail.com>
To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 3/3] signal.c: fix gcc warning on 32 bits kernel
Date: Fri, 9 Feb 2007 17:34:16 +0100	[thread overview]
Message-ID: <61ec3ea90702090834k774bf18bwf7ec5f7b10349779@mail.gmail.com> (raw)
In-Reply-To: <20070210.011835.08318488.anemo@mba.ocn.ne.jp>

On 2/9/07, Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> On Fri,  9 Feb 2007 16:07:38 +0100, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> >       new_ka.sa.sa_handler = (__sighandler_t) __gu_tmp;
> >
> > Here we try to cast an 'unsigned long long' into a 32 bits pointer and
> > that's the reason of the warning.
>
> This line is never executed on 32bit kernel and gcc optimize out.  On

yes I agree but it seems that gcc compiles this line before optimizing out...

>
> I think this is a problem of __get_user() implementation or gcc
> itself.  Though I can not find better solution yet, hacking the caller
> to avoid the warning would not be right things to to.

I agree too but I haven't found something else.

BTW, my version of gcc is: mipsel-linux-gcc (GCC) 3.4.4 mipssde-6.05.00-20061023

thanks
-- 
                Franck

  reply	other threads:[~2007-02-09 16:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 15:07 [PATCH 0/3] More signal clean up Franck Bui-Huu
2007-02-09 15:07 ` [PATCH 1/3] signal: avoid useless test in do_signal() Franck Bui-Huu
2007-02-09 16:21   ` Ralf Baechle
2007-02-09 16:50     ` Franck Bui-Huu
2007-02-09 15:07 ` [PATCH 2/3] signals: make common _BLOCKABLE macro Franck Bui-Huu
2007-02-13  1:39   ` Ralf Baechle
2007-02-09 15:07 ` [PATCH 3/3] signal.c: fix gcc warning on 32 bits kernel Franck Bui-Huu
2007-02-09 16:18   ` Atsushi Nemoto
2007-02-09 16:34     ` Franck Bui-Huu [this message]
2007-02-09 21:00       ` Ralf Baechle
2007-02-12  9:01         ` Franck Bui-Huu
2007-02-12 14:04           ` Ralf Baechle
2007-02-12 15:25             ` Atsushi Nemoto
2007-02-13  1:43               ` Ralf Baechle
2007-02-13  2:05                 ` Ralf Baechle
2007-02-13 17:17                   ` Franck Bui-Huu

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=61ec3ea90702090834k774bf18bwf7ec5f7b10349779@mail.gmail.com \
    --to=fbuihuu@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.