From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id DD78CDE1B6 for ; Fri, 12 Oct 2007 08:01:28 +1000 (EST) In-Reply-To: <18190.39864.4562.852292@cargo.ozlabs.ibm.com> References: <20071011071558.676463639@au1.ibm.com> <20071011072208.075979098@au1.ibm.com> <18190.39864.4562.852292@cargo.ozlabs.ibm.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2C31F1C3-3337-483B-A463-767459305F1E@kernel.crashing.org> From: Kumar Gala Subject: Re: [patch 1/2] Replace NT_PRXFPREG with ELF_CORE_XFPREG_TYPE #define Date: Thu, 11 Oct 2007 17:01:43 -0500 To: Paul Mackerras Cc: PowerPC dev list , Linux Kernel Mailing List List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Oct 11, 2007, at 4:55 PM, Paul Mackerras wrote: > Kumar Gala writes: > >>> #define ELF_CORE_XFPREG_TYPE to be NT_PRXFPREG in all current >>> users so >>> there's are no change in behaviour. >> >> Can we make this ELF_CORE_VECREG_TYPE or something that is so coupled >> to the x86 specific name? > > How is "extended floating point registers" x86-specific? we'll I don't consider the altivec register file as 'extended fp'. I'm assuming the name XFP came from IA32 land when MMX/SSE came into existence. > ELF_CORE_XFPREG_TYPE is a suitable name for something that's used in > conjunction with a function called elf_core_copy_task_xfpregs(). agreed, I think the function name should change as well. - k