riscv-gnu-toolchain/gcc.git - Unnamed repository; edit this file 'description' to name the repository.

Unnamed repository; edit this file 'description' to name the repository.

root

path: root/libjava/java/util/TreeMap$7.h

diff options

author	Kyrylo Tkachov <kyrylo.tkachov@arm.com>	2014-10-24 11:32:40 +0000
committer	Kyrylo Tkachov <ktkachov@gcc.gnu.org>	2014-10-24 11:32:40 +0000
commit	bc50815a52e938ad2c7d5f594e7cdac304d58284 (patch)
tree	7c239104beb440f28829a3a2e1fc5eb70436b897 /libjava/java/util/TreeMap$7.h
parent	84a34193c2d20b71673cef216b94d27ca7525a95 (diff)
download	gcc-bc50815a52e938ad2c7d5f594e7cdac304d58284.zip gcc-bc50815a52e938ad2c7d5f594e7cdac304d58284.tar.gz gcc-bc50815a52e938ad2c7d5f594e7cdac304d58284.tar.bz2

[AArch64] LINK_SPEC changes for Cortex-A53 erratum 835769 workaround

* config/aarch64/aarch64-elf-raw.h (CA53_ERR_835769_SPEC): Define. (LINK_SPEC): Include CA53_ERR_835769_SPEC. * config/aarch64/aarch64-linux.h (CA53_ERR_835769_SPEC): Define. (LINK_SPEC): Include CA53_ERR_835769_SPEC. From-SVN: r216639

Diffstat (limited to 'libjava/java/util/TreeMap$7.h')

0 files changed, 0 insertions, 0 deletions

rom that, follow the Unix instructions in INSTALL. NOTE: "make test" and normal file operations may fail in directories mounted as text (i.e. mount -t c:\somewhere /home) due to Cygwin stripping of carriage returns. To avoid this ensure that a binary mount is used, e.g. mount -b c:\somewhere /home. It is also possible to create "conventional" Windows binaries that use the Microsoft C runtime system (msvcrt.dll or crtdll.dll) using MinGW development add-on for Cygwin. MinGW is supported even as a standalone setup as described in the following section. In the context you should recognize that binaries targeting Cygwin itself are not interchangeable with "conventional" Windows binaries you generate with/for MinGW. GNU C (MinGW/MSYS) ------------------ * Compiler and shell environment installation: MinGW and MSYS are available from http://www.mingw.org/, both are required. Run the installers and do whatever magic they say it takes to start MSYS bash shell with GNU tools and matching Perl on its PATH. "Matching Perl" refers to chosen "shell environment", i.e. if built under MSYS, then Perl compiled for MSYS must be used. Alternatively, one can use MSYS2 from https://msys2.github.io/, which includes MingW (32-bit and 64-bit). * It is also possible to cross-compile it on Linux by configuring with './Configure --cross-compile-prefix=i386-mingw32- mingw ...'. Other possible cross compile prefixes include x86_64-w64-mingw32- and i686-w64-mingw32-. Linking your application ------------------------ This section applies to non-Cygwin builds. If you link with static OpenSSL libraries then you're expected to additionally link your application with WS2_32.LIB, GDI32.LIB, ADVAPI32.LIB, CRYPT32.LIB and USER32.LIB. Those developing non-interactive service applications might feel concerned about linking with GDI32.LIB and USER32.LIB, as they are justly associated with interactive desktop, which is not available to service processes. The toolkit is designed to detect in which context it's currently executed, GUI, console app or service, and act accordingly, namely whether or not to actually make GUI calls. Additionally those who wish to /DELAYLOAD:GDI32.DLL and /DELAYLOAD:USER32.DLL and actually keep them off service process should consider implementing and exporting from .exe image in question own _OPENSSL_isservice not relying on USER32.DLL. E.g., on Windows Vista and later you could: __declspec(dllexport) __cdecl BOOL _OPENSSL_isservice(void) { DWORD sess; if (ProcessIdToSessionId(GetCurrentProcessId(),&sess)) return sess==0; return FALSE; } If you link with OpenSSL .DLLs, then you're expected to include into your application code small "shim" snippet, which provides glue between OpenSSL BIO layer and your compiler run-time. See the OPENSSL_Applink manual page for further details.


context:
space:
mode: