HomeSort by relevance Sort by last modified time
    Searched full:mapping (Results 1126 - 1150 of 5659) sorted by null

<<41424344454647484950>>

  /external/mesa3d/src/mesa/state_tracker/
st_cb_fbo.h 53 struct pipe_transfer *transfer; /**< only used when mapping the resource */
  /external/pdfium/core/src/fxge/fx_freetype/fxft2.5.01/src/sfnt/
ttcmap.h 5 /* TrueType character mapping table (cmap) support (specification). */
  /external/proguard/examples/ant/
applications2.xml 24 <!-- Save the obfuscation mapping to a file, and preserve line numbers. -->
  /external/proguard/examples/
applets.pro 14 # Save the obfuscation mapping to a file, so you can de-obfuscate any stack
applications.pro 18 # Save the obfuscation mapping to a file, so you can de-obfuscate any stack
library.pro 16 # Save the obfuscation mapping to a file, so we can de-obfuscate any stack
proguard.pro 17 # Write out an obfuscation mapping file, for de-obfuscating any stack traces
servlets.pro 15 # Save the obfuscation mapping to a file, so you can de-obfuscate any stack
  /external/proguard/examples/gradle/
applets.gradle 34 // Save the obfuscation mapping to a file, so you can de-obfuscate any stack
applications.gradle 38 // Save the obfuscation mapping to a file, so you can de-obfuscate any stack
midlets.gradle 57 // Save the obfuscation mapping to a file, so you can de-obfuscate any stack
proguard.gradle 37 // Write out an obfuscation mapping file, for de-obfuscating any stack traces
proguardgui.gradle 41 // perform incremental obfuscation based on its mapping file, and only keep the
servlets.gradle 35 // Save the obfuscation mapping to a file, so you can de-obfuscate any stack
  /external/proguard/src/proguard/
ProGuard.java 320 // We'll apply a mapping, if requested.
323 System.out.println("Applying mapping [" + fileName(configuration.applyMapping) + "]");
326 // We'll print out the mapping, if requested.
329 System.out.println("Printing mapping to [" + fileName(configuration.printMapping) + "]...");
  /external/qemu/distrib/sdl-1.2.15/docs/man3/
SDL_SetColors.3 17 Palettized (8-bit) screen surfaces with the \fBSDL_HWPALETTE\fP flag have two palettes, a logical palette that is used for mapping blits to/from the surface and a physical palette (that determines how the hardware will map the colors to the display)\&. \fBSDL_SetColors\fP modifies both palettes (if present), and is equivalent to calling \fISDL_SetPalette\fR with the \fBflags\fR set to \fB(SDL_LOGPAL | SDL_PHYSPAL)\fP\&.
SDL_SetPalette.3 13 Palettized (8-bit) screen surfaces with the \fBSDL_HWPALETTE\fP flag have two palettes, a logical palette that is used for mapping blits to/from the surface and a physical palette (that determines how the hardware will map the colors to the display)\&. \fISDL_BlitSurface\fR always uses the logical palette when blitting surfaces (if it has to convert between surface pixel formats)\&. Because of this, it is often useful to modify only one or the other palette to achieve various special color effects (e\&.g\&., screen fading, color flashes, screen dimming)\&.
  /external/skia/include/ports/
SkFontMgr_indirect.h 89 * For data caching we want a mapping from data id to weak references to
  /external/skia/src/gpu/
GrDrawTargetCaps.h 45 * Indicates whether GPU->CPU memory mapping for GPU resources such as vertex buffers and
  /external/skia/src/ports/
SkOSFile_win.cpp 85 //TODO: use SK_TRACEHR(GetLastError(), "Could not create file mapping.") to report.
  /external/srec/portable/src/
PFileSystemImpl.c 30 * [file path, PFileSystem*] mapping.
  /external/srec/tools/thirdparty/OpenFst/fst/lib/
relabel.h 34 // mapping.
37 // \param relabel_pairs vector of pairs indicating old to new mapping
91 // mapping.
94 // \param new_symbols symbol set indicating new mapping
  /external/strace/xlat/
mmap_flags.h 38 * required you to specify the mapping address;
  /external/valgrind/main/coregrind/
pub_core_debuginfo.h 45 /* LINUX: Notify the debuginfo system about a new mapping, or the
47 mapping. This is the way new debug information gets loaded. If
48 allow_SkFileV is True, it will try load debug info if the mapping
55 refer to the debuginfo read as a result of this specific mapping,
  /external/valgrind/main/docs/internals/
segments-seginfos.txt 58 ELF file via a mapping this way (which would probably upset Valgrind no
94 > possibly: mapping is > 1 page (catches the case of mapping first
97 > If the client wants to subsequently chop up the mapping, or change its

Completed in 330 milliseconds

<<41424344454647484950>>