lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 12 Sep 2006 21:31:52 +0000
From:	Frederik Deweerdt <deweerdt@...e.fr>
To:	Zach Brown <zach.brown@...cle.com>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	rmk+kernel@....linux.org.uk
Subject: Re: [-mm patch] arm build fail: vfpsingle.c

On Tue, Sep 12, 2006 at 12:07:35PM -0700, Zach Brown wrote:
> 
> > Yes it does, but the intended use of 'func' (or so I understood) is to
> > print the calling function name, not the current function's, isn't it?
> 
> Dunno, I took it to mean the current function from the context of that
> patch.  I could be wrong, of course.
I've just checked, this are some of the callers of
vfp_single_normaliseround (last argument is 'func'):

in vfp_single_fuito: 
	vfp_single_normaliseround(sd, &vs, fpscr, 0, "fuito");
in vfp_single_fsito:
	vfp_single_normaliseround(sd, &vs, fpscr, 0, "fsito");
in vfp_single_fnmul:
	vfp_single_normaliseround(sd, &vsd, fpscr, exceptions, "fnmul");

It definitely looks like we want the calling function to be printed
here.

Regards,
Frederik

> 
> - z
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ