kc3-lang/libffi/src/ia64/ffitarget.h

• Show log

  Commit

• Hash : 11de69dd
  Author :
  Date : 2018-02-11T11:29:39
  

  ia64: fix variadic function closures with FP arguments
  
  libffi test framework already flagged failures as:
  
  ```
      FAIL: libffi.call/cls_double_va.c -W -Wall -Wno-psabi -O0 output pattern test, is 7.0
      res: 4
      0.0
      res: 4
      ? should match 7.0
      ?es: 4
      ?.0
      res: 4
  ```
  
  Failure happens here at
  
  ```c
      // testsuite/libffi.call/cls_double_va.c
      ...
      char*  format    = "%.1f\n";
      double doubleArg = 7;
      ...
      CHECK(ffi_prep_closure_loc(pcl, &cif, cls_double_va_fn, NULL,
                                 code) == FFI_OK);
      res = ((int(*)(char*, ...))(code))(format, doubleArg);
  ```
  
  libffi expects 'doubleArg' to be located in 'f9' (second FP argument) but
  gcc placed it to 'r33' (second GR).
  
  ia64 software [1] manual described argument passing ABI in
  "8.5.2 Register Parameters" as:
  
  """
      If an actual parameter is known to correspond to a floating-point
      formal parameter, the following rules apply:
      a) The actual parameter is passed in the next available floating-point
         parameter register, if one is available. Floating-point parameter
         registers are allocated as needed from the range f8-f15, starting
         with f8.
      b) If all available floating-point parameter registers have been used,
         the actual parameter is passed in the appropriate general register(s).
         (This case can occur only as a result of homogeneous floating-point
         aggregates, described below.)
  
      If a floating-point actual parameter is known to correspond to
      a variable-argument specification in  the formal parameter list,
      the following rule applies:
      c) The actual parameter is passed in the appropriate general
         register(s).
  
      If the compiler cannot determine, at the point of call,
      whether the corresponding formal parameter is a varargs parameter,
      it must generate code that satisfies both of the above conditions.
      (The compiler’s determination may be based on prototype declarations,
      language standard assumptions,  analysis, or other user options or
      information.)
  """
  
  We have [c] case here and gcc uses only GR for parameter passing.
  
  The change binds known variadic arguments ro GRs instead of FPs as those
  are always expected to be initialized for all variadic call types.
  
  This fixes all 10 failures on ia64-unknown-linux-gnu:
  
  ```
                   === libffi Summary ===
      -# of expected passes            1945
      -# of unexpected failures        10
      +
      +# of expected passes            1955
  ```
  
  [1]: https://www.intel.com/content/dam/www/public/us/en/documents/guides/itanium-software-runtime-architecture-guide.pdf
  
  Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
  

Download

• src/ia64/ffitarget.h

• /* -----------------------------------------------------------------*-C-*-
     ffitarget.h - Copyright (c) 2012  Anthony Green
                   Copyright (c) 1996-2003  Red Hat, Inc.
     Target configuration macros for IA-64.
  
     Permission is hereby granted, free of charge, to any person obtaining
     a copy of this software and associated documentation files (the
     ``Software''), to deal in the Software without restriction, including
     without limitation the rights to use, copy, modify, merge, publish,
     distribute, sublicense, and/or sell copies of the Software, and to
     permit persons to whom the Software is furnished to do so, subject to
     the following conditions:
  
     The above copyright notice and this permission notice shall be included
     in all copies or substantial portions of the Software.
  
     THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND,
     EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
     MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
     NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
     HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
     WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
     DEALINGS IN THE SOFTWARE.
  
     ----------------------------------------------------------------------- */
  
  #ifndef LIBFFI_TARGET_H
  #define LIBFFI_TARGET_H
  
  #ifndef LIBFFI_H
  #error "Please do not include ffitarget.h directly into your source.  Use ffi.h instead."
  #endif
  
  #ifndef LIBFFI_ASM
  typedef unsigned long long          ffi_arg;
  typedef signed long long            ffi_sarg;
  
  typedef enum ffi_abi {
    FFI_FIRST_ABI = 0,
    FFI_UNIX,   	/* Linux and all Unix variants use the same conventions	*/
    FFI_LAST_ABI,
    FFI_DEFAULT_ABI = FFI_UNIX
  } ffi_abi;
  #endif
  
  /* ---- Definitions for closures ----------------------------------------- */
  
  #define FFI_CLOSURES 1
  #define FFI_TRAMPOLINE_SIZE 24  /* Really the following struct, which 	*/
  				/* can be interpreted as a C function	*/
  				/* descriptor:				*/
  #define FFI_TARGET_SPECIFIC_VARIADIC 1
  #define FFI_EXTRA_CIF_FIELDS unsigned nfixedargs
  
  #endif
  

Download