HomeSort by relevance Sort by last modified time
    Searched full:convention (Results 351 - 375 of 1639) sorted by null

<<11121314151617181920>>

  /external/llvm/test/CodeGen/X86/
hipe-cc64.ll 3 ; Check the HiPE calling convention works (x86-64)
win32_sret.ll 11 ; is callee-cleanup. However, in MSVC's cdecl calling convention, sret pointer
win_ftol2.ll 10 ; function has a nonstandard calling convention: the input value is expected on
  /external/llvm/utils/TableGen/
TableGen.cpp 59 "Generate calling convention descriptions"),
  /external/oprofile/libopagent/
opagent.h 49 * using the naming convention <process_id>.dump.
  /external/qemu/distrib/jpeg-6b/
coderules.doc 29 with two spaces per indentation level. (This indentation convention is
  /external/qemu/distrib/sdl-1.2.15/
README.Watcom 71 The library can also be built with the stack calling convention of the
  /external/sepolicy/
README 116 for the user, it is convention to specify tags and options in all uppercase
  /external/skia/src/gpu/gl/win/
GrGLCreateNativeInterface_win.cpp 19 * Otherwise, a springboard would be needed that hides the calling convention.
  /external/svox/pico/compat/src/com/android/tts/compat/
CompatTtsService.java 56 // to be loaded. By convention, if an engine wants the TTS framework to pass
  /external/wpa_supplicant_8/src/drivers/
driver_hostap.h 14 /* New wireless extensions API - SET/GET convention (even ioctl numbers are
  /external/zlib/src/contrib/delphi/
zlibd32.mak 7 # This project uses the Delphi (fastcall/register) calling convention:
  /external/zlib/src/contrib/pascal/
zlibd32.mak 7 # This project uses the Delphi (fastcall/register) calling convention:
  /frameworks/base/docs/html/guide/topics/manifest/
meta-data-element.jd 55 Java-style naming convention &mdash; for example,
  /frameworks/base/docs/html/training/backward-compatible-ui/
new-implementation.jd 48 <p>A good naming convention for this implementation is to append the API level or platform version code name corresponding to the APIs required by the concrete classes. For example, the native tab implementation can be provided by <code>CompatTabHoneycomb</code> and <code>TabHelperHoneycomb</code> classes, since they rely on APIs available in Android 3.0 (API level 11) or later.</p>
  /libcore/dom/src/test/java/org/w3c/domts/
JTidyDOMImplementation.java 33 * name. To avoid possible conflicts, as a convention, names referring
  /libcore/luni/src/main/native/
java_lang_ProcessManager.cpp 157 // Execute process. By convention, the first argument in the arg array
  /ndk/build/core/
default-build-commands.mk 23 # IMPORTANT: The result must use the host path convention.
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/detail/
workaround.hpp 24 // and all earlier versions of a compiler, the following convention
  /packages/apps/Email/tests/src/com/android/email/activity/
MessageViewTests.java 86 // * The name 'test preconditions' is a convention to signal that if this
  /sdk/eclipse/plugins/com.android.ide.eclipse.tests/src/com/android/ide/eclipse/tests/
AdtTestData.java 92 // On Windows, uniformize all separators to use the / convention
  /sdk/eclipse/plugins/com.android.ide.eclipse.tests/unittests/com/android/ide/eclipse/adt/internal/sdk/
LayoutParamsParserTest.java 38 * Convention: method names that start with an underscore are actually local wrappers
  /hardware/invensense/60xx/mlsdk/mllite/
mlarray.c 261 * Euler angles are returned according to the X convention.
262 * This is typically the convention used for mobile devices where the X
319 * Euler angles are returned according to the Y convention.
320 * This convention is typically used in augmented reality applications,
376 * This convention is mostly used in application involving the use
378 * is along the Z axis. In this convention roll is defined as the
380 * Euler angles are returned according to the Y convention.
    [all...]
  /external/chromium_org/native_client_sdk/src/libraries/third_party/newlib-extras/netinet/
in.h 242 * that is (by convention) restricted to privileged processes. This
243 * convention is based on "vouchsafe" principles only. It is only secure
  /external/chromium_org/third_party/libusb/src/libusb/
libusb.h 94 * libusbx's Windows calling convention.
98 * convention</em> (calling convention: the manner in which parameters are
101 * Matching the Windows API itself, libusbx uses the WINAPI convention (which
102 * translates to the <tt>stdcall</tt> convention) and guarantees that the
105 * convention, even if another convention is being used by default within
111 * convention.
    [all...]

Completed in 1710 milliseconds

<<11121314151617181920>>