search for: operating_system

...ence while parsing or normalizing. > > > > So here’s what I would suggest. > > > > 1. Define the target triple as follows (adapted from Triple.h): > > > > /// Target triples are strings in the canonical form: > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT > > > > 2....

...l enumeration, the triple parser should be able to handle it presence or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object forma...

...ng.**** > > ** ** > > So here’s what I would suggest.**** > > ** ** > > **1. **Define the target triple as follows (adapted from Triple.h):* > *** > > ** ** > > /// Target triples are strings in the canonical form:**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM**** > > /// or**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT **** > > /// or**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT**** > > /// or**** > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT**** > &gt...

...l enumeration, the triple parser should be able to handle it presence or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object forma...

...l enumeration, the triple parser should be able to handle it presence or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object forma...

...andle it presence or absence while parsing or normalizing. > > So here’s what I would suggest. > > 1. Define the target triple as follows (adapted from Triple.h): > > > > /// Target triples are strings in the canonical form: > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT > > /// or > > /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT > > > > 2....

...ng or normalizing. >> >> So here’s what I would suggest. >> >> 1. Define the target triple as follows (adapted from Triple.h): >> >> >> >> /// Target triples are strings in the canonical form: >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM >> >> /// or >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT >> >> /// or >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT >> >> /// or >> >> /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FO...

...new releases, as it takes quite a while on my older hardware. Thank you. P.S. If anyone needs to build a release for themselves, I believe the process is: clone LLVM from github - https://github.com/llvm-mirror/llvm get target OS darwin version from here: https://en.wikipedia.org/wiki/Darwin_(operating_system) - in the example below I'm building for 14.5.0 llvm/utils/release/test-release.sh -release 6.0.0 -final -triple x86_64-apple-darwin14.5.0 results in: llvm/utils/release/final/clang+llvm-6.0.0-x86_64-apple-darwin14.5.0.tar.xz -------------- next part -------------- An HTML attachment was scru...

On Wed, Jul 25, 2012 at 12:24 AM, Kaylor, Andrew <andrew.kaylor at intel.com>wrote: > > -------------------------------**** > > ELF Support on Windows**** > > -------------------------------**** > > **** > > There are various reasons that it would be nice to be able to support > generation of ELF objects on Windows through the MCJIT interface, one of >

...> > P.S. If anyone needs to build a release for themselves, I believe the process is: > > clone LLVM from github - https://github.com/llvm-mirror/llvm <https://github.com/llvm-mirror/llvm> > > get target OS darwin version from here: https://en.wikipedia.org/wiki/Darwin_(operating_system) <https://en.wikipedia.org/wiki/Darwin_(operating_system)> - in the example below I'm building for 14.5.0 > > llvm/utils/release/test-release.sh -release 6.0.0 -final -triple x86_64-apple-darwin14.5.0 > > results in: llvm/utils/release/final/clang+llvm-6.0.0-x86_64-apple-dar...

...l enumeration, the triple parser should be able to handle it presence or absence while parsing or normalizing. So here’s what I would suggest. 1. Define the target triple as follows (adapted from Triple.h): /// Target triples are strings in the canonical form: /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT /// or /// ARCHITECTURE-VENDOR-OPERATING_SYSTEM-OBJECT_FORMAT-ENVIRONMENT 2. Add an llvm::Triple::ObjectFormatType enum with all llvm-supported object forma...

...f anyone wants to volunteer to be the "publicity coordinator", that would be great. I''m sure I''ll forget to update the RAA listing when we update each version, for example. And I just noticed that dmoz has a category waiting for us: http://dmoz.org/Computers/Software/Operating_Systems/Graphic_Subsystems/Toolkits/wxWindows/ Kevin

...ry this mailing list, maybe there are some experts who know what they're talking about. Please refer to my experts-exchange question, all the required information will be there. It is more practical to send you to the webpage than paste out what I've done. http://www.experts-exchange.com/Operating_Systems/Linux/Q_21882610.html Hope any can help find THE solution.

...>> Thank you. >> >> P.S. If anyone needs to build a release for themselves, I believe the process is: >> >> clone LLVM from github - https://github.com/llvm-mirror/llvm >> >> get target OS darwin version from here: https://en.wikipedia.org/wiki/Darwin_(operating_system) - in the example below I'm building for 14.5.0 >> >> llvm/utils/release/test-release.sh -release 6.0.0 -final -triple x86_64-apple-darwin14.5.0 >> >> results in: llvm/utils/release/final/clang+llvm-6.0.0-x86_64-apple-darwin14.5.0.tar.xz >> >> >> &...

Hi All, I think Im having a mental block here. For some reason I just cant get my head round relationships. What I have is the following. 4 tables 1) Hosts 2) Software 3) OperatingSystem 4) Company In my terms (which are most likely wrong) a company can have lots of hosts, a host has lots of software, a host has one operating system. So should my models have the following relations in them?

I am trying to set up a flexible infrastructure for the assembly code. Basically what I want is configure.in determination of basic machine type (intel/compatible, alpha, ppc), then within that (say intel) the code will detect variants like MMX, SSE, and use the right routines. I know how to do the second, but what is a good way to do the first? Linux/Cygwin/Solaris seem to support the MACHTYPE

...;>> >>> P.S. If anyone needs to build a release for themselves, I believe the process is: >>> >>> clone LLVM from github - https://github.com/llvm-mirror/llvm >>> >>> get target OS darwin version from here: https://en.wikipedia.org/wiki/Darwin_(operating_system) - in the example below I'm building for 14.5.0 >>> >>> llvm/utils/release/test-release.sh -release 6.0.0 -final -triple x86_64-apple-darwin14.5.0 >>> >>> results in: llvm/utils/release/final/clang+llvm-6.0.0-x86_64-apple-darwin14.5.0.tar.xz >>> &...

>>>>> I?aki ?car writes: Same from here: in addition to what the standards say, it always pays to be defensive and check "Portable Shell Programming" in the Autoconf manual. Among other things, this says '$((EXPRESSION))' Arithmetic expansion is not portable as some shells (most notably Solaris 10 '/bin/sh') don't support it. motivating

...have many uses. I.e.: - Plugins - Separating/protecting execution contexts. Like processes without the overhead of changing address space. - Controlled injection of user-level code into a monolithic kernel. - Provide safety in a Singularity-like kernel (http://en.wikipedia.org/wiki/Singularity_(operating_system)). Now, my question is whether LLVM is suited for this type of use and, if so, are there any projects that work towards this goal? At the top of my head, I guess a transform that detects illegal memory references, a way to call external functions safely and some kind of tracking of external r...

...386 compatible? > (i386, i586, i686, athlon? etc). The best way to do this is to let autoconf work its magic for you. Use AC_CANONICAL_TARGET in configure.in, and it will place canonical system type for the target in the shell variable 'target' in the form CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM. Be sure to use the target, not the host, to allow cross-compiling. It will also be broken out into target_cpu, target_vendor and target_os. So you can use $target_cpu for your tests. A simple: case $target_cpu in i*86) blahblah ;; powerpc) blahblah ;; sparc) blahblah ;; esac should do...