AWS::Events::EventBusPolicy
The
AWS::Events::EventBusPolicy
resource creates an event bus policy for Amazon CloudWatch Events. An event bus
policy enables your account to receive events from other AWS accounts. These events
can trigger CloudWatch Events rules created
in your account. For more information, see
Sending and Receiving Events
Between AWS Accounts in the Amazon CloudWatch Events User Guide.
Note
If you grant permission to other accounts using Condition
and specifying an organization, then accounts in that
organization must specify a RoleArn
with proper permissions
when they use PutTarget
to add your account's event bus as a
target.
Syntax
To declare this entity in your AWS CloudFormation template, use the following syntax:
JSON
{ "Type" : "AWS::Events::EventBusPolicy", "Properties" : { "Action" :
String
, "Condition" : Condition, "Principal" :String
, "StatementId" :String
} }
YAML
Type: "AWS::Events::EventBusPolicy" Properties: Action:
String
Condition: Condition Principal:String
StatementId:String
Properties
Action
-
The action that you are enabling the other account to perform. Currently, this must be
events:PutEvents
.Required: Yes
Type: String
Update requires: No interruption
Condition
-
A JSON string which you can use to limit the event bus permissions you are granting to only accounts that fulfill the condition. Currently, the only supported condition is membership in a certain AWS organization. The string must contain
Type
,Key
, andValue
fields.Currently, the
Type
must beStringEquals
, theKey
must beaws:PrincipalOrgID
, and theValue
field specifies the ID of the AWS organization.If you specify
Condition
with an AWS organization ID, you must specify "*" as the value forPrincipal
. This grants permission to all the accounts in the named organization.Required: No
Type: Condition
Update requires: No interruption
Principal
-
The 12-digit AWS account ID that you are permitting to put events to your default event bus. Specify
*
to permit any account to put events to your default event bus, or if you are specifying an organization ID in theCondition
object.Required: Yes
Type: String
Update requires: No interruption
StatementId
-
An identifier string for the external account to which you are granting permissions. To later revoke the permission for this external account, you need to know this string.
Required: Yes
Type: String
Update requires: Replacement
Return Values
Ref
When you pass the logical ID of an
AWS::Events::EventBusPolicy
resource to the intrinsic
Ref
function, the function returns the
event bus policy ID, such as
EventBusPolicy-1aBCdeFGh2J3
.
For more information, see Ref.
Examples
Grant Permission to One Account
The following example grants permission to one AWS account with an account ID of<PHONE_NUMBER>33
.
JSON
"SampleEventBusPolicy": { "Type": "AWS::Events::EventBusPolicy", "Properties": { "Action": "events:PutEvents", "Principal": "111122223333", "StatementId": "MyStatement" } }
YAML
SampleEventBusPolicy: Type: AWS::Events::EventBusPolicy Properties: Action: "events:PutEvents" Principal: "111122223333" StatementId: "MyStatement"
Grant Permission to an Organization
The following example grants permission to all AWS accounts in the organization with
an organization ID of o-1234567890
.
JSON
"SampleEventBusPolicy": { "Type": "AWS::Events::EventBusPolicy", "Properties": { "Action": "events:PutEvents", "Principal": "*", "StatementId": "MyStatement", "Condition": { "Type": "StringEquals", "Key": "aws:PrincipalOrgID", "Value": "o-1234567890" } } }
YAML
SampleEventBusPolicy: Type: AWS::Events::EventBusPolicy Properties: Action: "events:PutEvents" Principal: "*" StatementId: "MyStatement" Condition: Type: "StringEquals" Key: "aws:PrincipalOrgID" Value: "o-1234567890"
See Also
-
Sending and Receiving Events Between AWS Accounts in the Amazon CloudWatch User Guide
-
PutPermission in the Amazon CloudWatch API Reference


Converts from the specified encoding to the internal XMLCh* encoding.
- Parameters
-
| data | the source buffer to be transcoded |
| length | the length of the source buffer |
| encoding | the name of the encoding to transcode to |
| manager | the memory manager to use |
Converts from the specified encoding to the internal XMLCh* encoding.
- Parameters
-
| data | the source buffer to be transcoded |
| length | the length of the source buffer |
| trans | the transcoder to use |
| manager | the memory manager to use |
| TranscodeFromStr::~TranscodeFromStr |
( |
| ) |
|
| XMLCh * TranscodeFromStr::adopt |
( |
| ) |
|
Returns the transcoded, null terminated string - adopting the memory allocated to it from the TranscodeFromStr object.
- Returns
- the transcoded string
Returns the length of the transcoded string in characters.
The length does not include the null terminator.
- Returns
- the length of the transcoded string in characters
| const XMLCh * TranscodeFromStr::str |
( |
| ) |
const |
Returns the transcoded, null terminated string.
- Returns
- the transcoded string
The documentation for this class was generated from the following file:


Hi my name is Suthunya (pronounce Su-tan-ya) I know you are not and will not be the only one having a hard time pronouncing my name. I was born and raised in Thailand and I love to challenge myself.
When I was in the University, I challenged myself, after graduated I would be living independently outside of country. It was like a day dream for me in my early 20's with no connection. But I accomplished my challenge, I got a job in USA and moved here the day after graduation.
A few months after, I diagnosed as a severe allergy. I had to get a series of shots so I could live my life less suffer unless I do exercise regularly. I had never done any kind of sport or exercise before but for a better health I challenged myself that I would train and run half marathon! It was rough, so many attempts and failures. But I accomplished my challenge! I finished 3 half marathon in Las Vegas and on 2018 I moved to Seattle, WA., I finished 2 half marathon and 5k run within the same year!
There are a few more challenges I had accomplished. Now I'm challenge myself learning Web Developer which I have zero background about it. It is tough but I know by heart that I will accomplish and become one of a great web Developer out there.


| deployName: | |
| creatorType: | |
| creatorId: | |
| namespace: | image: |
| tag: | |
| cpu: | |
| memory: | |
| env key: | |
| env value: | |
| env description: | |
|
|
|
|
|
|
| replicas: | |
| cluster name: | |
| hostEnv: | |
| log path: | |
| autoCollect (true or false): | |
| logTopic: | |
|
|
|
| label name: | |
| label content: | |
|
|
|
| load balance port: | |
| load balance target port: | |
| health check type: | |
| health check port: | |
| health check timeout: | |
| health check timeout number: | |
| health check url: | |
| deployId: | |
| version: | |
| 回滚 deployId: | |
| 回滚 version: | |
| 扩容 deployId: | |
| 扩容 replicas: | |
| 缩容 deployId: | |
| 缩容 replicas: | |
| ----------------openxxs is handsome---------------- | |
| deployId: | image: |
| tag: | |
| cpu: | |
| memory: | |
| env key: | |
| env value: | |
| env description: | |
|
|
|
|
|
|
| log path: | |
| autoCollect (true or false): | |
| logTopic: | |
|
|
|
| label name: | |
| label content: | |
|
|
|
| 升级: ---> |
| 获取 deployId: |
| 停止 deployId: | ||
| 删除 deployId: | ||
| 测试监控: | 跳转监控页面 |


Lisa Deborah Frank (born April 21, 1955) is an American businesswoman, the founder of Lisa Frank Incorporated, headquartered in Tucson, Arizona. She is known for producing whimsical commercial design for school supplies and other products that are primarily marketed to children. Frank is the founder and CEO of Lisa Frank Incorporated. Frank founded the company in 1979 at the age of 24, and continues to lead it as of 2019. Her corporation's artwork features rainbow and neon colors and stylized depictions of animals, including dolphins, pandas, and unicorns. In the 1980s and 1990s, her products – including school supplies such as lunchboxes and Trapper Keepers, as well as toys and stickers – were popular among elementary and middle school-aged girls. The company's headquarters is in Tucson, Arizona.
In 2011, she launched a colorful line of clothing. Frank partnered with Reebok to release two versions of limited-release Reebok Classic Leathers shoes in 2017. In 2017, Entertainment Weekly reported that the designer was partnering with producer Jon Shestack to develop a movie inspired by her work. In 2019, Frank designed the logo for John Mayer's Instagram television series, Current Mood. Frank is "notoriously elusive and private." In a 2012 interview with Urban Outfitters, they agreed to obscure her face. She is an alumna of the Kingswood School (today: Cranbrook Kingswood School), a preparatory school in Bloomfield Hills, Michigan. Her father was an art collector and introduced her to the work of Pop Art artists like Peter Max. In 2005 Lisa Frank divorced James Green, the CEO and co-share holder of Lisa Frank Incorporated. The court agreed to assign control of the company to Lisa Frank.


We are creating business, security, machine learning, mobile and web application.
Business software set of computer programs used by business users to perform various business functions. These business applications are used to increase productivity, to measure productivity and to perform other business functions accurately.
Application security encompasses measures taken to improve the security of an application often by finding, fixing and preventing security vulnerabilities.
A mobile application, is a software application designed to run on a mobile device, and a web application is an application software that runs on a web server.
We have developed a product with high efficiency and bug-free. Most of our products are open source and cross-platform. We also developed some commercial business applications for data scientists. We also developed web-based security applications and API based mobile applications.
Here our SDT team members. All the members are very co-operative and energetic. They are very passionate to work with this field and all have a vision to developed those particular fields.


in (inches), mm (millimeters).
May be a fractional value, which is a floating point number appended with either % or %p, such as "14.5%
".
The % suffix always means a percentage of the base size; the optional %p suffix provides a size relative to
some parent container.
This may also be a reference to a resource (in the form
"@[package:]type:name
") or
theme attribute (in the form
"?[package:][type:]name
")
containing a value of this type.
public static final int windowMinWidthMajor
May be a dimension value, which is a floating point number appended with a unit such as "14.5sp
".
Available units are: px (pixels), dp (density-independent pixels), sp (scaled pixels based on preferred font size),
in (inches), mm (millimeters).
May be a fractional value, which is a floating point number appended with either % or %p, such as "14.5%
".
The % suffix always means a percentage of the base size; the optional %p suffix provides a size relative to
some parent container.
This may also be a reference to a resource (in the form
"@[package:]type:name
") or
theme attribute (in the form
"?[package:][type:]name
")
containing a value of this type.
public static final int windowMinWidthMinor
May be a dimension value, which is a floating point number appended with a unit such as "14.5sp
".
Available units are: px (pixels), dp (density-independent pixels), sp (scaled pixels based on preferred font size),
in (inches), mm (millimeters).
May be a fractional value, which is a floating point number appended with either % or %p, such as "14.5%
".
The % suffix always means a percentage of the base size; the optional %p suffix provides a size relative to
some parent container.
This may also be a reference to a resource (in the form
"@[package:]type:name
") or
theme attribute (in the form
"?[package:][type:]name
")
containing a value of this type.
public static final int windowNoTitle
Must be a boolean value, either "true
" or "false
".
This may also be a reference to a resource (in the form
"@[package:]type:name
") or
theme attribute (in the form
"?[package:][type:]name
")
containing a value of this type.


Welcome to Silicon Trail.
Begin game
Copyright International Corporations (TM) Forever
Made by
Michael
and
Jason


--- title: Callback Core keywords: fastai sidebar: home_sidebar summary: "Base callback class" description: "Base callback class" nb_path: "nbs/12_callback_core.ipynb" ---
The training cycle in MRL is built around the Callback system. Rather than trying to explicitly define every training cycle variant, Callbacks define a series of events (see Events
) that occur during training and allow users to easily hook into those events. The result is an extremely flexible framework that can adapt to most generative design challenges.
Callbacks use the __call__
function to organize events. The call function will be passed an event name, like compute_reward
. If the Callback function has an attribute that matches the event name, the attribute is called.
Callbacks have access to the training environment (see Environment
) and can access the training environment, the model/agent, the training buffer, training log, other callbacks and all other aspects of the training state
The BatchState
class is used by an Environment
to track values generated or computed during a batch. Every batch, the old BatchState
is deleted and a new BatchState
is created.
Attributes in BatchState
can be set or accessed with a key like a dictionary or as an attribute. BatchState
can hold any arbitrary value during a batch. However, it was designed for the use case where every attribute is either a single value or a list/container with length equal to the current batch size.
BatchState
holds the rewards
value for a batch. All reward functions should ultimately add their reward value to BatchState.rewards
. See Reward
for more information.
BatchState
holds the loss
value for a batch. This is the value that will be backpropagated during the optimizer update. All loss functions should ultimately add their value to BatchState.loss
. See Loss
for more information.


At Slices we pride ourselves in being your neighborhood pizzeria. Our New York authentic pie are built to order using homemade recipes from our family archives. Our motto is local, fresh, fast! We love to source our produce locally, we make all of our doughs and sauces fresh daily and our pies cook up in a New York minute. Our dough and sauces are made fresh, daily using only the best ingredients. Once you taste a Slices you'll be hooked! Our quality and flavor far surpass the competition and we're sure you'll feel the same way. Slices is truly a modern classic. It is a place where each guest has the opportunity to custom build their own dining experience.


About me
Home
Settings
Locate Cinema:
Whats on:
Your Bio:
Movie Ark Search
Your Bio:
Hello
Your biography information is currently stored below:
Your name:
Your favourite movie:
Your favourite genre:
Help
To use this application please ensure that you enable location services.
(c)2017 All Rights Reserved


Premium
Volkswagen - SUV
Competently embrace dynamic intellectual capital.
Features20000KMs
5 Seater
Black
20kmpl
Competently embrace dynamic intellectual capital.
Features


Transport CSS Demo
Demonstrates how to use
Zapatec.Transport.loadCss
to import a CSS file into the web page.
Load CSS file sample.css
to add a background image and change the font and border of the div.
This is sample div.
Show the CSS file
.
This page uses an
AJAX Component
- Zapatec DHTML Transport Widget, but your browser does not support Javascript.


Giuliani Officially Has Legal Representation
Trump lawyer Rudy Giuliani has finally rustled up some lawyers of his own as his role in the Ukraine scandal grows ever clearer.
Giuliani has been without representation, though in the market, since he and attorney Jon Sale parted ways in October.
He has denied a congressional subpoena to testify about his role at the center of the pressure campaign to coerce Ukraine to manufacture a scandal centering on the Bidens.
Costello’s name may sound familiar due to a conversation he had with Michael Cohen in 2018. In emails provided to Congress and obtained by CNN, he said that Giuliani could “sleep well tonight” because he had “friends in high places,” a seeming allusion to a presidential pardon.
Costello, who has been friends with Giuliani for decades, called that interpretation of the conversation “nonsense.” He was reportedly considering representing Cohen for a time.


git-mailsplit - Simple UNIX mbox splitter program
git mailsplit [-b] [-f<nn>] [-d<prec>] [--keep-cr] -o<directory> [--] [(<mbox>|<Maildir>)...]
Splits a mbox file or a Maildir into a list of files: "0001" "0002" .. in the specified directory so you can process them further from there.
Important
Maildir splitting relies upon filenames being sorted to output patches in the correct order.
<mbox>
Mbox file to split. If not given, the mbox is read from the standard input.
<Maildir>
Root of the Maildir to split. This directory should contain the cur, tmp and new subdirectories.
-o<directory>
Directory in which to place the individual messages.
-b
If any file doesn(cqt begin with a From line, assume it is a single mail message instead of signaling error.
-d<prec>
Instead of the default 4 digits with leading zeros, different precision can be specified for the generated filenames.
-f<nn>
Skip the first <nn> numbers, for example if -f3 is specified, start the numbering with 0004.
--keep-cr
Do not remove er from lines ending with eren.
Part of the git(1) suite


А blockchain, originally block chain, is a growing list of records, called blocks, that are linked using cryptography. Each block contains a cryptographic hash of the previous block, a timestamp, and transaction data (generally represented as a Merkle tree).
digital ledger.
Blockchain security methods include the use of public-key cryptography.
Proof-of-work vs Proof-of-stake
The block time is the average time it takes for the network to generate one extra block in the blockchain. Some blockchains create a new block as frequently as every five seconds. By the time of block completion, the included data becomes verifiable. In cryptocurrency, this is practically when the transaction takes place, so a shorter block time means faster transactions. The block time for Ethereum is set to between 14 and 15 seconds, while for bitcoin it is on average 10 minutes.
Sometimes separate blocks can be produced concurrently, creating a temporary fork.
Thus, Blockchain is a new highlysecured, decentralized, distributed, public tecknology, which is integrating at more and more spheres of life making them simplier, cheaper, faster, safer. I think in near future majority of our population will become familiar to it as it was with web.


Click here
to view the online version.
100% Purchase Protection
Genuine Products | Secure Payments | Easy Returns
Dab your favourite perfume or wear the hottest shade of lipstick. Go ahead, grab all the attention this festive season.
or more on
Personal Care appliances
Diet and Nutrition bestsellers
Smell good.
Bestsellers in fragrances
© 2012-2014, Amazon Inc.


Getting Started with the LLVM System¶
- Overview
- Getting Started Quickly (A Summary)
- Requirements
- Getting Started with LLVM
- Directory Layout
- An Example Using the LLVM Tool Chain
- Common Problems
- Links
Overview¶
Welcome to LLVM! In order to get started, you first need to know some basic information.
First, LLVM comes in three pieces. The first piece is the LLVM suite. This contains all of the tools, libraries, and header files needed to use LLVM. It contains an assembler, disassembler, bitcode analyzer and bitcode optimizer. It also contains basic regression tests that can be used to test the LLVM tools and the Clang front end.
The second piece is the Clang front end. This component compiles C, C++, Objective C, and Objective C++ code into LLVM bitcode. Once compiled into LLVM bitcode, a program can be manipulated with the LLVM tools from the LLVM suite.
There is a third, optional piece called Test Suite. It is a suite of programs with a testing harness that can be used to further test LLVM’s functionality and performance.
Getting Started Quickly (A Summary)¶
The LLVM Getting Started documentation may be out of date. So, the Clang Getting Started page might also be a good place to start.
Here’s the short story for getting up and running quickly with LLVM:
Read the documentation.
Read the documentation.
Remember that you were warned twice about reading the documentation.
- In particular, the relative paths specified are important.
Checkout LLVM:
cd where-you-want-llvm-to-live
svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
Checkout Clang:
cd where-you-want-llvm-to-live
cd llvm/tools
svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
Checkout Extra Clang Tools [Optional]:
cd where-you-want-llvm-to-live
cd llvm/tools/clang/tools
svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk extra
Checkout LLD linker [Optional]:
cd where-you-want-llvm-to-live
cd llvm/tools
svn co http://llvm.org/svn/llvm-project/lld/trunk lld
Checkout Polly Loop Optimizer [Optional]:
cd where-you-want-llvm-to-live
cd llvm/tools
svn co http://llvm.org/svn/llvm-project/polly/trunk polly
Checkout Compiler-RT (required to build the sanitizers) [Optional]:
cd where-you-want-llvm-to-live
cd llvm/projects
svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt
Checkout Libomp (required for OpenMP support) [Optional]:
cd where-you-want-llvm-to-live
cd llvm/projects
svn co http://llvm.org/svn/llvm-project/openmp/trunk openmp
Checkout libcxx and libcxxabi [Optional]:
cd where-you-want-llvm-to-live
cd llvm/projects
svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx
svn co http://llvm.org/svn/llvm-project/libcxxabi/trunk libcxxabi
Get the Test Suite Source Code [Optional]
cd where-you-want-llvm-to-live
cd llvm/projects
svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Configure and build LLVM and Clang:
Warning: Make sure you’ve checked out all of the source code before trying to configure with cmake. cmake does not pickup newly added source directories in incremental builds.
The build uses CMake. LLVM requires CMake 3.4.3 to build. It is generally recommended to use a recent CMake, especially if you’re generating Ninja build files. This is because the CMake project is constantly improving the quality of the generators, and the Ninja generator gets a lot of attention.
cd where you want to build llvm
mkdir build
cd build
cmake -G <generator> [options] <path to llvm sources>
Some common generators are:
Unix Makefiles
— for generating make-compatible parallel makefiles.Ninja
— for generating Ninja build files. Most llvm developers use Ninja.Visual Studio
— for generating Visual Studio projects and solutions.Xcode
— for generating Xcode projects.
Some Common options:
-DCMAKE_INSTALL_PREFIX=directory
— Specify for directory the full pathname of where you want the LLVM tools and libraries to be installed (default/usr/local
).-DCMAKE_BUILD_TYPE=type
— Valid options for type are Debug, Release, RelWithDebInfo, and MinSizeRel. Default is Debug.-DLLVM_ENABLE_ASSERTIONS=On
— Compile with assertion checks enabled (default is Yes for Debug builds, No for all other build types).
Run your build tool of choice!
- The default target (i.e.
make
) will build all of LLVM - The
check-all
target (i.e.make check-all
) will run the regression tests to ensure everything is in working order. - CMake will generate build targets for each tool and library, and most
LLVM sub-projects generate their own
check-<project>
target. - Running a serial build will be slow. Make sure you run a
parallel build; for
make
, usemake -j
.
- The default target (i.e.
For more information see CMake
If you get an “internal compiler error (ICE)” or test failures, see below.
Consult the Getting Started with LLVM section for detailed information on configuring and compiling LLVM. Go to Directory Layout to learn about the layout of the source code tree.
Requirements¶
Before you begin to use the LLVM system, review the requirements given below. This may save you some trouble by knowing ahead of time what hardware and software you will need.
Hardware¶
LLVM is known to work on the following host platforms:
| OS | Arch | Compilers |
|---|---|---|
| Linux | x861 | GCC, Clang |
| Linux | amd64 | GCC, Clang |
| Linux | ARM4 | GCC, Clang |
| Linux | PowerPC | GCC, Clang |
| Solaris | V9 (Ultrasparc) | GCC |
| FreeBSD | x861 | GCC, Clang |
| FreeBSD | amd64 | GCC, Clang |
| NetBSD | x861 | GCC, Clang |
| NetBSD | amd64 | GCC, Clang |
| MacOS X2 | PowerPC | GCC |
| MacOS X | x86 | GCC, Clang |
| Cygwin/Win32 | x861, 3 | GCC |
| Windows | x861 | Visual Studio |
| Windows x64 | x86-64 | Visual Studio |
Note
- Code generation supported for Pentium processors and up
- Code generation supported for 32-bit ABI only
- To use LLVM modules on Win32-based system, you may configure LLVM
with
-DBUILD_SHARED_LIBS=On
. - MCJIT not working well pre-v7, old JIT engine not supported any more.
Note that Debug builds require a lot of time and disk space. An LLVM-only build will need about 1-3 GB of space. A full build of LLVM and Clang will need around 15-20 GB of disk space. The exact space requirements will vary by system. (It is so large because of all the debugging information and the fact that the libraries are statically linked into multiple tools).
If you you are space-constrained, you can build only selected tools or only selected targets. The Release build requires considerably less space.
The LLVM suite may compile on other platforms, but it is not guaranteed to do so. If compilation is successful, the LLVM utilities should be able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code generation should work as well, although the generated native code may not work on your platform.
Software¶
Compiling LLVM requires that you have several software packages installed. The table below lists those required packages. The Package column is the usual name for the software package that LLVM depends on. The Version column provides “known to work” versions of the package. The Notes column describes how LLVM uses the package and provides other details.
| Package | Version | Notes |
|---|---|---|
| GNU Make | 3.79, 3.79.1 | Makefile/build processor |
| GCC | >=4.8.0 | C/C++ compiler1 |
| python | >=2.7 | Automated test suite2 |
| zlib | >=<IP_ADDRESS> | Compression library3 |
Note
- Only the C and C++ languages are needed so there’s no need to build the other languages for LLVM’s purposes. See below for specific version info.
- Only needed if you want to run the automated test suite in the
llvm/test
directory. - Optional, adds compression / uncompression capabilities to selected LLVM tools.
Additionally, your compilation host is expected to have the usual plethora of Unix utilities. Specifically:
- ar — archive library builder
- bzip2 — bzip2 command for distribution generation
- bunzip2 — bunzip2 command for distribution checking
- chmod — change permissions on a file
- cat — output concatenation utility
- cp — copy files
- date — print the current date/time
- echo — print to standard output
- egrep — extended regular expression search utility
- find — find files/dirs in a file system
- grep — regular expression search utility
- gzip — gzip command for distribution generation
- gunzip — gunzip command for distribution checking
- install — install directories/files
- mkdir — create a directory
- mv — move (rename) files
- ranlib — symbol table builder for archive libraries
- rm — remove (delete) files and directories
- sed — stream editor for transforming output
- sh — Bourne shell for make build scripts
- tar — tape archive for distribution generation
- test — test things in file system
- unzip — unzip command for distribution checking
- zip — zip command for distribution generation
Host C++ Toolchain, both Compiler and Standard Library¶
LLVM is very demanding of the host C++ compiler, and as such tends to expose bugs in the compiler. We are also planning to follow improvements and developments in the C++ language and library reasonably closely. As such, we require a modern host C++ toolchain, both compiler and standard library, in order to build LLVM.
For the most popular host toolchains we check for specific minimum versions in our build systems:
- Clang 3.1
- GCC 4.8
- Visual Studio 2015 (Update 3)
Anything older than these toolchains may work, but will require forcing the build system with a special option and is not really a supported host platform. Also note that older versions of these compilers have often crashed or miscompiled LLVM.
For less widely used host toolchains such as ICC or xlC, be aware that a very recent version may be required to support all of the C++ features used in LLVM.
We track certain versions of software that are known to fail when used as part of the host toolchain. These even include linkers at times.
GNU ld 2.16.X. Some 2.16.X versions of the ld linker will produce very long
warning messages complaining that some “.gnu.linkonce.t.*
” symbol was
defined in a discarded section. You can safely ignore these messages as they are
erroneous and the linkage is correct. These messages disappear using ld 2.17.
GNU binutils 2.17: Binutils 2.17 contains a bug which causes huge link times (minutes instead of seconds) when building LLVM. We recommend upgrading to a newer version (<IP_ADDRESS>.4 or later).
GNU Binutils 2.19.1 Gold: This version of Gold contained a bug which causes intermittent failures when building LLVM with position independent code. The symptom is an error about cyclic dependencies. We recommend upgrading to a newer version of Gold.
Getting a Modern Host C++ Toolchain¶
This section mostly applies to Linux and older BSDs. On Mac OS X, you should have a sufficiently modern Xcode, or you will likely need to upgrade until you do. Windows does not have a “system compiler”, so you must install either Visual Studio 2015 or a recent version of mingw64. FreeBSD 10.0 and newer have a modern Clang as the system compiler.
However, some Linux distributions and some other or older BSDs sometimes have extremely old versions of GCC. These steps attempt to help you upgrade you compiler even on such a system. However, if at all possible, we encourage you to use a recent version of a distribution with a modern system compiler that meets these requirements. Note that it is tempting to to install a prior version of Clang and libc++ to be the host compiler, however libc++ was not well tested or set up to build on Linux until relatively recently. As a consequence, this guide suggests just using libstdc++ and a modern GCC as the initial host in a bootstrap, and then using Clang (and potentially libc++).
The first step is to get a recent GCC toolchain installed. The most common distribution on which users have struggled with the version requirements is Ubuntu Precise, 12.04 LTS. For this distribution, one easy option is to install the toolchain testing PPA and use it to install a modern GCC. There is a really nice discussions of this on the ask ubuntu stack exchange. However, not all users can use PPAs and there are many other distributions, so it may be necessary (or just useful, if you’re here you are doing compiler development after all) to build and install GCC from source. It is also quite easy to do these days.
Easy steps for installing GCC 4.8.2:
% wget https://ftp.gnu.org/gnu/gcc/gcc-4.8.2/gcc-4.8.2.tar.bz2
% wget https://ftp.gnu.org/gnu/gcc/gcc-4.8.2/gcc-4.8.2.tar.bz2.sig
% wget https://ftp.gnu.org/gnu/gnu-keyring.gpg
% signature_invalid=`gpg --verify --no-default-keyring --keyring ./gnu-keyring.gpg gcc-4.8.2.tar.bz2.sig`
% if [ $signature_invalid ]; then echo "Invalid signature" ; exit 1 ; fi
% tar -xvjf gcc-4.8.2.tar.bz2
% cd gcc-4.8.2
% ./contrib/download_prerequisites
% cd ..
% mkdir gcc-4.8.2-build
% cd gcc-4.8.2-build
% $PWD/../gcc-4.8.2/configure --prefix=$HOME/toolchains --enable-languages=c,c++
% make -j$(nproc)
% make install
For more details, check out the excellent GCC wiki entry, where I got most of this information from.
Once you have a GCC toolchain, configure your build of LLVM to use the new
toolchain for your host compiler and C++ standard library. Because the new
version of libstdc++ is not on the system library search path, you need to pass
extra linker flags so that it can be found at link time (-L
) and at runtime
(-rpath
). If you are using CMake, this invocation should produce working
binaries:
% mkdir build
% cd build
% CC=$HOME/toolchains/bin/gcc CXX=$HOME/toolchains/bin/g++ \
cmake .. -DCMAKE_CXX_LINK_FLAGS="-Wl,-rpath,$HOME/toolchains/lib64 -L$HOME/toolchains/lib64"
If you fail to set rpath, most LLVM binaries will fail on startup with a message
from the loader similar to libstdc++.so.6: version `GLIBCXX_3.4.20' not
found
. This means you need to tweak the -rpath linker flag.
When you build Clang, you will need to give it access to modern C++11
standard library in order to use it as your new host in part of a bootstrap.
There are two easy ways to do this, either build (and install) libc++ along
with Clang and then use it with the -stdlib=libc++
compile and link flag,
or install Clang into the same prefix ($HOME/toolchains
above) as GCC.
Clang will look within its own prefix for libstdc++ and use it if found. You
can also add an explicit prefix for Clang to look in for a GCC toolchain with
the --gcc-toolchain=/opt/my/gcc/prefix
flag, passing it to both compile and
link commands when using your just-built-Clang to bootstrap.
Getting Started with LLVM¶
The remainder of this guide is meant to get you up and running with LLVM and to give you some basic information about the LLVM environment.
The later sections of this guide describe the general layout of the LLVM source tree, a simple example using the LLVM tool chain, and links to find more information about LLVM or to get help via e-mail.
Terminology and Notation¶
Throughout this manual, the following names are used to denote paths specific to the local system and working environment. These are not environment variables you need to set but just strings used in the rest of this document below. In any of the examples below, simply replace each of these names with the appropriate pathname on your local system. All these paths are absolute:
SRC_ROOT
This is the top level directory of the LLVM source tree.
OBJ_ROOT
This is the top level directory of the LLVM object tree (i.e. the tree where object files and compiled programs will be placed. It can be the same as SRC_ROOT).
Unpacking the LLVM Archives¶
If you have the LLVM distribution, you will need to unpack it before you can begin to compile it. LLVM is distributed as a set of two files: the LLVM suite and the LLVM GCC front end compiled for your platform. There is an additional test suite that is optional. Each file is a TAR archive that is compressed with the gzip program.
The files are as follows, with x.y marking the version number:
llvm-x.y.tar.gz
Source release for the LLVM libraries and tools.
llvm-test-x.y.tar.gz
Source release for the LLVM test-suite.
Checkout LLVM from Subversion¶
If you have access to our Subversion repository, you can get a fresh copy of the entire source code. All you need to do is check it out from Subversion as follows:
cd where-you-want-llvm-to-live
- Read-Only:
svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
- Read-Write:
svn co<EMAIL_ADDRESS>llvm
This will create an ‘llvm
’ directory in the current directory and fully
populate it with the LLVM source code, Makefiles, test directories, and local
copies of documentation files.
If you want to get a specific release (as opposed to the most recent revision),
you can check it out from the ‘tags
’ directory (instead of ‘trunk
’). The
following releases are located in the following subdirectories of the ‘tags
’
directory:
- Release 3.5.0 and later: RELEASE_350/final and so on
- Release 2.9 through 3.4: RELEASE_29/final and so on
- Release 1.1 through 2.8: RELEASE_11 and so on
- Release 1.0: RELEASE_1
If you would like to get the LLVM test suite (a separate package as of 1.4), you get it from the Subversion repository:
% cd llvm/projects
% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
By placing it in the llvm/projects
, it will be automatically configured by
the LLVM cmake configuration.
Git Mirror¶
Git mirrors are available for a number of LLVM subprojects. These mirrors sync
automatically with each Subversion commit and contain all necessary git-svn
marks (so, you can recreate git-svn metadata locally). Note that right now
mirrors reflect only trunk
for each project. You can do the read-only Git
clone of LLVM via:
% git clone https://git.llvm.org/git/llvm.git/
If you want to check out clang too, run:
% cd llvm/tools
% git clone https://git.llvm.org/git/clang.git/
If you want to check out compiler-rt (required to build the sanitizers), run:
% cd llvm/projects
% git clone https://git.llvm.org/git/compiler-rt.git/
If you want to check out libomp (required for OpenMP support), run:
% cd llvm/projects
% git clone https://git.llvm.org/git/openmp.git/
If you want to check out libcxx and libcxxabi (optional), run:
% cd llvm/projects
% git clone https://git.llvm.org/git/libcxx.git/
% git clone https://git.llvm.org/git/libcxxabi.git/
If you want to check out the Test Suite Source Code (optional), run:
% cd llvm/projects
% git clone https://git.llvm.org/git/test-suite.git/
Since the upstream repository is in Subversion, you should use git
pull --rebase
instead of git pull
to avoid generating a non-linear history
in your clone. To configure git pull
to pass --rebase
by default on the
master branch, run the following command:
% git config branch.master.rebase true
Sending patches with Git¶
Please read Developer Policy, too.
Assume master
points the upstream and mybranch
points your working
branch, and mybranch
is rebased onto master
. At first you may check
sanity of whitespaces:
% git diff --check master..mybranch
The easiest way to generate a patch is as below:
% git diff master..mybranch > /path/to/mybranch.diff
It is a little different from svn-generated diff. git-diff-generated diff has
prefixes like a/
and b/
. Don’t worry, most developers might know it
could be accepted with patch -p1 -N
.
But you may generate patchset with git-format-patch. It generates by-each-commit patchset. To generate patch files to attach to your article:
% git format-patch --no-attach master..mybranch -o /path/to/your/patchset
If you would like to send patches directly, you may use git-send-email or git-imap-send. Here is an example to generate the patchset in Gmail’s [Drafts].
% git format-patch --attach master..mybranch --stdout | git imap-send
Then, your .git/config should have [imap] sections.
[imap]
host = imaps://imap.gmail.com
user =<EMAIL_ADDRESS>pass = himitsu!
port = 993
sslverify = false
; in English
folder = "[Gmail]/Drafts"
; example for Japanese, "Modified UTF-7" encoded.
folder = "[Gmail]/&Tgtm+DBN-"
; example for Traditional Chinese
folder = "[Gmail]/&g0l6Pw-"
For developers to work with git-svn¶
To set up clone from which you can submit code using git-svn
, run:
% git clone https://git.llvm.org/git/llvm.git/
% cd llvm
% git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=<username>
% git config svn-remote.svn.fetch :refs/remotes/origin/master
% git svn rebase -l # -l avoids fetching ahead of the git mirror.
# If you have clang too:
% cd tools
% git clone https://git.llvm.org/git/clang.git/
% cd clang
% git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=<username>
% git config svn-remote.svn.fetch :refs/remotes/origin/master
% git svn rebase -l
Likewise for compiler-rt, libomp and test-suite.
To update this clone without generating git-svn tags that conflict with the upstream Git repo, run:
% git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
% git checkout master
% git svn rebase -l
% (cd tools/clang &&
git checkout master &&
git svn rebase -l)
Likewise for compiler-rt, libomp and test-suite.
This leaves your working directories on their master branches, so you’ll need to
checkout
each working branch individually and rebase
it on top of its
parent branch.
For those who wish to be able to update an llvm repo/revert patches easily using
git-svn, please look in the directory for the scripts git-svnup
and
git-svnrevert
.
To perform the aforementioned update steps go into your source directory and
just type git-svnup
or git svnup
and everything will just work.
If one wishes to revert a commit with git-svn, but do not want the git hash to
escape into the commit message, one can use the script git-svnrevert
or
git svnrevert
which will take in the git hash for the commit you want to
revert, look up the appropriate svn revision, and output a message where all
references to the git hash have been replaced with the svn revision.
To commit back changes via git-svn, use git svn dcommit
:
% git svn dcommit
Note that git-svn will create one SVN commit for each Git commit you have pending,
so squash and edit each commit before executing dcommit
to make sure they all
conform to the coding standards and the developers’ policy.
On success, dcommit
will rebase against the HEAD of SVN, so to avoid conflict,
please make sure your current branch is up-to-date (via fetch/rebase) before
proceeding.
The git-svn metadata can get out of sync after you mess around with branches and
dcommit
. When that happens, git svn dcommit
stops working, complaining
about files with uncommitted changes. The fix is to rebuild the metadata:
% rm -rf .git/svn
% git svn rebase -l
Please, refer to the Git-SVN manual (man git-svn
) for more information.
For developers to work with a git monorepo¶
Note
This set-up is using an unofficial mirror hosted on GitHub, use with caution.
To set up a clone of all the llvm projects using a unified repository:
% export TOP_LEVEL_DIR=`pwd`
% git clone https://github.com/llvm-project/llvm-project-20170507/ llvm-project
% cd llvm-project
% git config branch.master.rebase true
You can configure various build directory from this clone, starting with a build of LLVM alone:
% cd $TOP_LEVEL_DIR
% mkdir llvm-build && cd llvm-build
% cmake -GNinja ../llvm-project/llvm
Or lldb:
% cd $TOP_LEVEL_DIR
% mkdir lldb-build && cd lldb-build
% cmake -GNinja ../llvm-project/llvm -DLLVM_ENABLE_PROJECTS=lldb
Or a combination of multiple projects:
% cd $TOP_LEVEL_DIR
% mkdir clang-build && cd clang-build
% cmake -GNinja ../llvm-project/llvm -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi"
A helper script is provided in llvm/utils/git-svn/git-llvm
. After you add it
to your path, you can push committed changes upstream with git llvm push
.
% export PATH=$PATH:$TOP_LEVEL_DIR/llvm-project/llvm/utils/git-svn/
% git llvm push
While this is using SVN under the hood, it does not require any interaction from
you with git-svn.
After a few minutes, git pull
should get back the changes as they were
committed. Note that a current limitation is that git
does not directly
record file rename, and thus it is propagated to SVN as a combination of
delete-add instead of a file rename.
The SVN revision of each monorepo commit can be found in the commit notes. git
does not fetch notes by default. The following commands will fetch the notes and
configure git to fetch future notes. Use git notes show $commit
to look up
the SVN revision of a git commit. The notes show up git log
, and searching
the log is currently the recommended way to look up the git commit for a given
SVN revision.
% git config --add remote.origin.fetch +refs/notes/commits:refs/notes/commits
% git fetch
If you are using arc to interact with Phabricator, you need to manually put it at the root of the checkout:
% cd $TOP_LEVEL_DIR
% cp llvm/.arcconfig ./
% mkdir -p .git/info/
% echo .arcconfig >> .git/info/exclude
Local LLVM Configuration¶
Once checked out from the Subversion repository, the LLVM suite source code must
be configured before being built. This process uses CMake.
Unlinke the normal configure
script, CMake
generates the build files in whatever format you request as well as various
*.inc
files, and llvm/include/Config/config.h
.
Variables are passed to cmake
on the command line using the format
-D<variable name>=<value>
. The following variables are some common options
used by people developing LLVM.
| Variable | Purpose |
|---|---|
| CMAKE_C_COMPILER | Tells cmake which C compiler to use. By
default, this will be /usr/bin/cc. |
| CMAKE_CXX_COMPILER | Tells cmake which C++ compiler to use. By
default, this will be /usr/bin/c++. |
| CMAKE_BUILD_TYPE | Tells cmake what type of build you are trying
to generate files for. Valid options are Debug,
Release, RelWithDebInfo, and MinSizeRel. Default
is Debug. |
| CMAKE_INSTALL_PREFIX | Specifies the install directory to target when running the install action of the build files. |
| LLVM_TARGETS_TO_BUILD | A semicolon delimited list controlling which
targets will be built and linked into llc. This is
equivalent to the --enable-targets option in
the configure script. The default list is defined
as LLVM_ALL_TARGETS , and can be set to include
out-of-tree targets. The default value includes:
AArch64, AMDGPU, ARM, BPF, Hexagon, Mips,
MSP430, NVPTX, PowerPC, Sparc, SystemZ, X86,
XCore . |
| LLVM_ENABLE_DOXYGEN | Build doxygen-based documentation from the source code This is disabled by default because it is slow and generates a lot of output. |
| LLVM_ENABLE_SPHINX | Build sphinx-based documentation from the source code. This is disabled by default because it is slow and generates a lot of output. Sphinx version 1.5 or later recommended. |
| LLVM_BUILD_LLVM_DYLIB | Generate libLLVM.so. This library contains a
default set of LLVM components that can be
overridden with LLVM_DYLIB_COMPONENTS . The
default contains most of LLVM and is defined in
tools/llvm-shlib/CMakelists.txt . |
| LLVM_OPTIMIZED_TABLEGEN | Builds a release tablegen that gets used during the LLVM build. This can dramatically speed up debug builds. |
To configure LLVM, follow these steps:
Change directory into the object root directory:
% cd OBJ_ROOT
Run the
cmake
:% cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=prefix=/install/path [other options] SRC_ROOT
Compiling the LLVM Suite Source Code¶
Unlike with autotools, with CMake your build type is defined at configuration. If you want to change your build type, you can re-run cmake with the following invocation:
% cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=type SRC_ROOT
Between runs, CMake preserves the values set for all options. CMake has the following build types defined:
Debug
These builds are the default. The build system will compile the tools and libraries unoptimized, with debugging information, and asserts enabled.
Release
For these builds, the build system will compile the tools and libraries with optimizations enabled and not generate debug info. CMakes default optimization level is -O3. This can be configured by setting theCMAKE_CXX_FLAGS_RELEASE
variable on the CMake command line.
RelWithDebInfo
These builds are useful when debugging. They generate optimized binaries with debug information. CMakes default optimization level is -O2. This can be configured by setting theCMAKE_CXX_FLAGS_RELWITHDEBINFO
variable on the CMake command line.
Once you have LLVM configured, you can build it by entering the OBJ_ROOT directory and issuing the following command:
% make
If the build fails, please check here to see if you are using a version of GCC that is known not to compile LLVM.
If you have multiple processors in your machine, you may wish to use some of the parallel build options provided by GNU Make. For example, you could use the command:
% make -j2
There are several special targets which are useful when working with the LLVM source code:
make clean
Removes all files generated by the build. This includes object files, generated C/C++ files, libraries, and executables.
make install
Installs LLVM header files, libraries, tools, and documentation in a hierarchy under$PREFIX
, specified withCMAKE_INSTALL_PREFIX
, which defaults to/usr/local
.
make docs-llvm-html
If configured with-DLLVM_ENABLE_SPHINX=On
, this will generate a directory atOBJ_ROOT/docs/html
which contains the HTML formatted documentation.
Cross-Compiling LLVM¶
It is possible to cross-compile LLVM itself. That is, you can create LLVM
executables and libraries to be hosted on a platform different from the platform
where they are built (a Canadian Cross build). To generate build files for
cross-compiling CMake provides a variable CMAKE_TOOLCHAIN_FILE
which can
define compiler flags and variables used during the CMake test operations.
The result of such a build is executables that are not runnable on on the build host but can be executed on the target. As an example the following CMake invocation can generate build files targeting iOS. This will work on Mac OS X with the latest Xcode:
% cmake -G "Ninja" -DCMAKE_OSX_ARCHITECTURES="armv7;armv7s;arm64"
-DCMAKE_TOOLCHAIN_FILE=<PATH_TO_LLVM>/cmake/platforms/iOS.cmake
-DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_RUNTIME=Off -DLLVM_INCLUDE_TESTS=Off
-DLLVM_INCLUDE_EXAMPLES=Off -DLLVM_ENABLE_BACKTRACES=Off [options]
<PATH_TO_LLVM>
Note: There are some additional flags that need to be passed when building for iOS due to limitations in the iOS SDK.
Check How To Cross-Compile Clang/LLVM using Clang/LLVM and Clang docs on how to cross-compile in general for more information about cross-compiling.
The Location of LLVM Object Files¶
The LLVM build system is capable of sharing a single LLVM source tree among several LLVM builds. Hence, it is possible to build LLVM for several different platforms or configurations using the same source tree.
Change directory to where the LLVM object files should live:
% cd OBJ_ROOT
Run
cmake
:% cmake -G "Unix Makefiles" SRC_ROOT
The LLVM build will create a structure underneath OBJ_ROOT that matches the
LLVM source tree. At each level where source files are present in the source
tree there will be a corresponding CMakeFiles
directory in the OBJ_ROOT.
Underneath that directory there is another directory with a name ending in
.dir
under which you’ll find object files for each source.
For example:
% cd llvm_build_dir % find lib/Support/ -name APFloat* lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
Optional Configuration Items¶
If you’re running on a Linux system that supports the binfmt_misc module, and you have root access on the system, you can set your system up to execute LLVM bitcode files directly. To do this, use commands like this (the first command may not be required if you are already using the module):
% mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
% echo ':llvm:M::BC::/path/to/lli:' > /proc/sys/fs/binfmt_misc/register
% chmod u+x hello.bc (if needed)
% ./hello.bc
This allows you to execute LLVM bitcode files directly. On Debian, you can also use this command instead of the ‘echo’ command above:
% sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
Directory Layout¶
One useful source of information about the LLVM source base is the LLVM doxygen documentation available at http://llvm.org/doxygen/. The following is a brief introduction to code layout:
llvm/examples
¶
Simple examples using the LLVM IR and JIT.
llvm/include
¶
Public header files exported from the LLVM library. The three main subdirectories:
llvm/include/llvm
All LLVM-specific header files, and subdirectories for different portions of LLVM:Analysis
,CodeGen
,Target
,Transforms
, etc…
llvm/include/llvm/Support
Generic support libraries provided with LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities and a Command Line option processing library store header files here.
llvm/include/llvm/Config
Header files configured by theconfigure
script. They wrap “standard” UNIX and C header files. Source code can include these header files which automatically take care of the conditional #includes that theconfigure
script generates.
llvm/lib
¶
Most source files are here. By putting code in libraries, LLVM makes it easy to share code among the tools.
llvm/lib/IR/
Core LLVM source files that implement core classes like Instruction and BasicBlock.
llvm/lib/AsmParser/
Source code for the LLVM assembly language parser library.
llvm/lib/Bitcode/
Code for reading and writing bitcode.
llvm/lib/Analysis/
A variety of program analyses, such as Call Graphs, Induction Variables, Natural Loop Identification, etc.
llvm/lib/Transforms/
IR-to-IR program transformations, such as Aggressive Dead Code Elimination, Sparse Conditional Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global Elimination, and many others.
llvm/lib/Target/
Files describing target architectures for code generation. For example,llvm/lib/Target/X86
holds the X86 machine description.
llvm/lib/CodeGen/
The major parts of the code generator: Instruction Selector, Instruction Scheduling, and Register Allocation.
llvm/lib/MC/
(FIXME: T.B.D.) ….?
llvm/lib/ExecutionEngine/
Libraries for directly executing bitcode at runtime in interpreted and JIT-compiled scenarios.
llvm/lib/Support/
Source code that corresponding to the header files inllvm/include/ADT/
andllvm/include/Support/
.
llvm/projects
¶
Projects not strictly part of LLVM but shipped with LLVM. This is also the directory for creating your own LLVM-based projects which leverage the LLVM build system.
llvm/test
¶
Feature and regression tests and other sanity checks on LLVM infrastructure. These are intended to run quickly and cover a lot of territory without being exhaustive.
test-suite
¶
A comprehensive correctness, performance, and benchmarking test suite for LLVM. Comes in a separate Subversion module because not every LLVM user is interested in such a comprehensive suite. For details see the Testing Guide document.
llvm/tools
¶
Executables built out of the libraries
above, which form the main part of the user interface. You can always get help
for a tool by typing tool_name -help
. The following is a brief introduction
to the most important tools. More detailed information is in
the Command Guide.
bugpoint
bugpoint
is used to debug optimization passes or code generation backends by narrowing down the given test case to the minimum number of passes and/or instructions that still cause a problem, whether it is a crash or miscompilation. See HowToSubmitABug.html for more information on usingbugpoint
.
llvm-ar
The archiver produces an archive containing the given LLVM bitcode files, optionally with an index for faster lookup.
llvm-as
The assembler transforms the human readable LLVM assembly to LLVM bitcode.
llvm-dis
The disassembler transforms the LLVM bitcode to human readable LLVM assembly.
llvm-link
llvm-link
, not surprisingly, links multiple LLVM modules into a single program.
lli
lli
is the LLVM interpreter, which can directly execute LLVM bitcode (although very slowly…). For architectures that support it (currently x86, Sparc, and PowerPC), by default,lli
will function as a Just-In-Time compiler (if the functionality was compiled in), and will execute the code much faster than the interpreter.
llc
llc
is the LLVM backend compiler, which translates LLVM bitcode to a native code assembly file.
opt
opt
reads LLVM bitcode, applies a series of LLVM to LLVM transformations (which are specified on the command line), and outputs the resultant bitcode. ‘opt -help
’ is a good way to get a list of the program transformations available in LLVM.
opt
can also run a specific analysis on an input LLVM bitcode file and print the results. Primarily useful for debugging analyses, or familiarizing yourself with what an analysis does.
llvm/utils
¶
Utilities for working with LLVM source code; some are part of the build process because they are code generators for parts of the infrastructure.
codegen-diff
codegen-diff
finds differences between code that LLC generates and code that LLI generates. This is useful if you are debugging one of them, assuming that the other generates correct output. For the full user manual, run`perldoc codegen-diff'
.
emacs/
Emacs and XEmacs syntax highlighting for LLVM assembly files and TableGen description files. See theREADME
for information on using them.
getsrcs.sh
Finds and outputs all non-generated source files, useful if one wishes to do a lot of development across directories and does not want to find each file. One way to use it is to run, for example:xemacs `utils/getsources.sh`
from the top of the LLVM source tree.
llvmgrep
Performs anegrep -H -n
on each source file in LLVM and passes to it a regular expression provided onllvmgrep
’s command line. This is an efficient way of searching the source base for a particular regular expression.
makellvm
Compiles all files in the current directory, then compiles and links the tool that is the first argument. For example, assuming you are inllvm/lib/Target/Sparc
, ifmakellvm
is in your path, runningmakellvm llc
will make a build of the current directory, switch to directoryllvm/tools/llc
and build it, causing a re-linking of LLC.
TableGen/
Contains the tool used to generate register descriptions, instruction set descriptions, and even assemblers from common TableGen description files.
vim/
vim syntax-highlighting for LLVM assembly files and TableGen description files. See theREADME
for how to use them.
An Example Using the LLVM Tool Chain¶
This section gives an example of using LLVM with the Clang front end.
Example with clang¶
First, create a simple C file, name it ‘hello.c’:
#include <stdio.h> int main() { printf("hello world\n"); return 0; }
Next, compile the C file into a native executable:
% clang hello.c -o hello
Note
Clang works just like GCC by default. The standard -S and -c arguments work as usual (producing a native .s or .o file, respectively).
Next, compile the C file into an LLVM bitcode file:
% clang -O3 -emit-llvm hello.c -c -o hello.bc
The -emit-llvm option can be used with the -S or -c options to emit an LLVM
.ll
or.bc
file (respectively) for the code. This allows you to use the standard LLVM tools on the bitcode file.Run the program in both forms. To run the program, use:
% ./hello
and
% lli hello.bc
The second examples shows how to invoke the LLVM JIT, lli.
Use the
llvm-dis
utility to take a look at the LLVM assembly code:% llvm-dis < hello.bc | less
Compile the program to native assembly using the LLC code generator:
% llc hello.bc -o hello.s
Assemble the native assembly language file into a program:
% /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native # On Solaris % gcc hello.s -o hello.native # On others
Execute the native code program:
% ./hello.native
Note that using clang to compile directly to native code (i.e. when the
-emit-llvm
option is not present) does steps 6/7/8 for you.
Common Problems¶
If you are having problems building or using LLVM, or if you have any other general questions about LLVM, please consult the Frequently Asked Questions page.
Links¶
This document is just an introduction on how to use LLVM to do some simple things… there are many more interesting and complicated things that you can do that aren’t documented here (but we’ll gladly accept a patch if you want to write something up!). For more information about LLVM, check out:


- Andrea Authoriser
- Casterbridge College
- UKPRN:12345678
Declaration submitted for 2017 to 2018
Submitted by Jim Riaz on 25 Oct 2017 at 11:59
We've sent you a confirmation email
What happens next?
You can return to this service if your subcontracting information changes or you have new subcontractors to declare.
Or you may want to:
Feedback survey
If you have a few moments then please complete our survey
It takes approximately 2 minutes and will help us to develop and improve this service.


[Page 35]
BERNAFAY WOOD
Friday 5
Now I am, cook to the officerís wonder how Iíll shape
Saturday 6
Im no good at cooking a girlís job and Iím all boy
Sunday 7
Aeroplanes in galore tis a sunny day & I kind of feel happy
A good week but, all the same it was hard, ďah me"


Add a comment...
Fill in the blanks below to add a comment. The only blanks that you
have
to fill in are the comments and name section. Thanks!
Your Name:
E-Mail:
URL:
City:
, State:
Country:
Comments:
*
*
Back to the Guestbook Entries
©2003 Ellipsis Design. All rights reserved.


@jwasserstein
A mechanical engineer learning software!
View your cars
None.
8.7 seconds
155 hp
150 ft-lb
4.5 seconds
70 hp
45 ft-lb


Documentation is the castor oil of programming. Managers think it is good for programmers and programmers hate it!. --Gerald Weinberg [ source]


We are never empty handed towards our dribbble community.
space trips
magic potions
does this button do?
One lonely ginger tried to learn french over night, but he f*ked up and now he speaks only about eggs and cheese.
My name is Mandark and I am Dexter's rival. He and I have been competing in science and other things for years and this race is just one more of those things where we try to beat each other, except I try to win by being sneaky and bad!
Mandark, Dexter’s rival
In a world where nobody understands him and his brilliant mind.
Le' Download" the genius "
Dexter is an extremely intelligent boy (a self described "Boy Genius") who has been creating fantastic inventions since he was a baby. He considers Albert
+ more" the sister "
Dee Dee is Dexter's extremely ditzy, simple-minded, energetic, hyperactive older sister, who inexplicably makes "squishy" sounds with her
+ more" the rival "
Dexter's arch-nemesis.  Share & Like :)


[1]
ultracompact, multiple face detection; fuzzy, digitized pictures indoors
[2]
nice size camera; Got snowed on ! so it quit.


India
Become A Partner
Login
Register
Moseva
Home
Categories
Categorie 1
Electrician
Solar
Web Design & Development
Interior Design
Categorie 2
Painter
Photo Shooting
Plumber
Event Management
Categorie 3
House Cleaning
Civil Work
Mover & Packer
Carpenter
Categorie 4
Beauty & SPA
Tour and Travel
Register
Home
Register
Name
Email Address
Password
Register
Term and Conditions
Already have an account?
Sign In
Connect with Facebook
Connect with Google


Top: Introduction
Basic features
Threads and synchronization primitives solve the vital problem of diversity of the threading API's on different platforms. The library also offers message queues and job queues as additional methods of thread synchronization and maintenance.
IP socket classes and utilities provide complete IP-based framework for both client-side and server-side programming. Combined with PTypes multithreading, these classes can be used for designing complex non-visual applications, such like network daemons or web robots.
Dynamic strings, variants, character sets, date/time type and various kinds of dynamic and associative arrays: Delphi programmers will find them very similar to the ones in their favorite language. The collection of these basic data types may be useful, among other things, for building compilers and interpreters for higher-level languages.
Streaming interfaces provide buffered I/O with simple and powerful text parsing methods. A strictly defined syntax for a given text format or a formal language can be represented by calls to PTypes token extraction methods. The unified streaming interface is applicable to files, named pipes and network sockets.
Special thread class with enhanced functionality called unit. Units have their own main() and input/output 'plugs'; they can be connected to each other within one application to form pipes, like processes in the UNIX shell.
Finally, everything above is portable: all platform-dependent details are hidden inside.
Why use PTypes?
PTypes is yet another generic class library among tens and hundreds of others. To find its own niche in this variety of generic programming tools we decided to emphasis on simplicity of the interfaces and readability of the resulting code (i.e. the code that uses the library). The library focuses only on most widely used data types and functional interfaces. We think that like programming languages themselves, low-level libraries, too, should use the minimal set of notions for covering most programming patterns.
Some data types in the library (strings, character sets and variants) use algebraic notation rather than object-oriented, i.e. you write length(s) for a string object instead of s.length(). We believe that traditional notation better fits to a class that represents some fundamental notion and is not supposed to produce subclasses with overridden methods. In other words, if there is no inheritance and polymorphism, there is no need for method calls as well.
PTypes uses old-fashioned all-lowercase naming style, since it can peacefully co-exist with other styles in one program. Whether you are a `unixoid' or you are using modern writing styles (Hungarian, Borland, etc.) you can combine your favorite style with PTypes with no or very little harm to your source code.
And finally, in order to achieve better readability of the resulting code we use clean class naming, i.e. the string type is called string, thread is thread, etc.
We designed this library in the hope that PTypes with its conciseness and intuitiveness could find its own 'target audience'.
Versions and availability
Version 2.0 of PTypes is the tenth public release. The third number in the version indicates insignificant improvements or bug fixes. You might want to take a look at the Changes page if you are familiar with one of the previous versions.
The latest source code and both on-line and out-of-line documentation can be found at
You can receive announcements about new releases through one of the following services:
Subscribe to the project at freshmeat.net
Monitor the project at SourceForge.netThe development version of PTypes is available at SourceForge.net's CVS server. If you are willing to join the development of the library, please become a SourceForge.net user and then contact me to get full access to the CVS repository. The file TODO in the development branch contains the immediate development plan for the library.
Bugs and known problems
The list of problems encountered in the latest version along with their solutions, if available, can be found at PTypes project management page (at SourceForge.net):
Contributors
We would like to thank:
Pierre-Frederic Caillaud <peufeu at free dot fr>
Ralph Siemsen <ralphs at netwinder dot org>
Marco Geri <m.geri at list dot it>
Philippe Le Rohellec <plerohel at hotmail dot com>
Mark Lentczner <markl at glyphic dot com>
Jordan Ritter <jpr5 at darkridge dot com>
Sergey Matveychuk <sem at ciam dot ru>
Contacts
PTypes is open and free, which also means it is open to your comments and suggestions. Please, submit bug reports and feature requests through PTypes project management page at sf.net. There is a public discussion forum for general questions.
The author would be grateful if you let him know that you use the library in your project. The author's email address is:
Hovik Melikyan <hovik at melikyan dot com>
See also: Compiling and Porting, Changes, Resources


Home Page
Cycle 8
What I did
This week was an interesting one. We did soldering and electronics, and I am impressively bad at soldering.
The electronics portion went well, making circuits using a kit and a BreadBoard. We had to make 10, as seen below.
After finishing these circuits, we had to then make a clock from a kit, soldering all the pieces
onto a circuit board. This process seemed to be going well for me until I finished, when the clock,
when plugged in, only showed faint numbers on half the screen and beeped at random times. I'm not sure
why this happened, but I think I will stick to buying completed clocks from now on.


---
layout: default
title: Components
---
Dozens of reusable components built to provide navigation, alerts, popovers, and more.Components
Toggleable, contextual menu for displaying lists of links. Made interactive with the dropdown JavaScript plugin.
Wrap the dropdown's trigger and the dropdown menu within .dropdown
, or another element that declares position: relative;
. Then add the menu's HTML.
Add .pull-right
to a .dropdown-menu
to right align the dropdown menu.
Add .disabled
to a

in the dropdown to disable the link.
Add an extra level of dropdown menus, appearing on hover like those of OS X, with some simple markup additions. Add .dropdown-submenu
to any li
in an existing dropdown menu for automatic styling.
Provide pagination links for your site or app with the multi-page pagination component, or the simpler pager alternative.
Simple pagination inspired by Rdio, great for apps and search results. The large block is hard to miss, easily scalable, and provides large click areas.
{% highlight html linenos %} {% endhighlight %}Links are customizable for different circumstances. Use .disabled
for unclickable links and .active
to indicate the current page.
You can optionally swap out active or disabled anchors for
to remove click functionality while retaining intended styles.
Fancy larger or smaller pagination? Add .pagination-large
, .pagination-small
, or .pagination-mini
for additional sizes.
Quick previous and next links for simple pagination implementations with light markup and styles. It's great for simple sites like blogs or magazines.
By default, the pager centers links.
{% highlight html linenos %} {% endhighlight %}Alternatively, you can align each link to the sides:
{% highlight html linenos %} {% endhighlight %}Pager links also use the general .disabled
utility class from the pagination.
Add any of the below mentioned modifier classes to change the appearance of a label.
| Labels | Markup |
|---|---|
| Default |
Default
|
| Success |
Success
|
| Warning |
Warning
|
| Danger |
Danger
|
| Info |
Info
|
Easily highlight new or unread items by adding a
to links, Bootstrap navs, and more.
When there are no new or unread items, badges will simply collapse (via CSS's :empty
selector) provided no content exists within.
Built-in styles are included for placing badges in active states in pill and list navigations.
A lightweight, flexible component to showcase key content on your site. It works well on marketing and content-heavy sites.
This is a simple hero unit, a simple jumbotron-style component for calling extra attention to featured content or information.
A simple shell for an h1
to appropriately space out and segment sections of content on a page. It can utilize the h1
's default small
, element as well most other components (with additional styles).
Extend Bootstrap's grid system with the thumbnail component to easily display grids of images, videos, text, and more.
By default, Bootstrap's thumbnails are designed to showcase linked images with minimal required markup.
{% highlight html linenos %} {% endhighlight %}With a bit of extra markup, it's possible to add any kind of HTML content like headings, paragraphs, or buttons into thumbnails.
Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages. For inline dismissal, use the alerts jQuery plugin.
Wrap any text and an optional dismiss button in .alert
for a basic warning alert message. To ensure proper behavior across all devices, be sure to use <button>
element with the data-dismiss="alert"
data attribute.
For longer messages, increase the padding on the top and bottom of the alert wrapper by adding .alert-block
.
Best check yo self, you're not looking too good. Nulla vitae elit libero, a pharetra augue. Praesent commodo cursus magna, vel scelerisque nisl consectetur et.
...
Add optional classes to change an alert's connotation.
Provide up-to-date feedback on the progress of a workflow or action with simple yet flexible progress bars.
Progress bars use CSS3 transitions and animations to achieve some of their effects. These features are not supported in IE8-9 or older versions of Firefox. Internet Explorer 10 and below, as well as Opera 12, do not support animations.
Default progress bar with a vertical gradient.
Progress bars use some of the same button and alert classes for consistent styles.
Uses a gradient to create a striped effect. Not available in IE8.
Add .active
to .progress-striped
to animate the stripes right to left. Not available in all versions of IE.
Place multiple bars into the same .progress
to stack them.
Abstract object styles for building various types of components (like blog comments, Tweets, etc) that feature a left- or right-aligned image alongside textual content.
The default media allow to float a media object (images, video, audio) to the left or right of a content block.
With a bit of extra markup, you can use media inside list (useful for comment threads or articles lists).
Cras sit amet nibh libero, in gravida nulla. Nulla vel metus scelerisque ante sollicitudin commodo. Cras purus odio, vestibulum in vulputate at, tempus viverra turpis.
Use the well as a simple effect on an element to give it an inset effect.
Control padding and rounded corners with two optional modifier classes.
Use the generic close icon for dismissing content like modals and alerts.
Simple, focused classes for small display or behavior tweaks.
Float an element left
{% highlight html linenos %}Float an element right
{% highlight html linenos %}Change an element's color to #999
...
{% endhighlight %} {% highlight css linenos %} .muted { color: #999; } {% endhighlight %}Clear the float
on any element. Utilizes the micro clearfix as popularized by Nicolas Gallagher.


CryptoCash NEWS
A Simple One Stop Shop for Your Cryptocurrency News
Invest in Crypto Here...
Coinbase
Robinhood
BlockFi
Gemini
eToro
Binance
Exodus
More...
$earch
Card1
Card2
Card3
Card4
Card5


Class yii\httpclient\Request
| Inheritance | yii\httpclient\Request » yii\httpclient\Message » yii\base\Component » yii\base\BaseObject |
|---|---|
| Implements | yii\base\Configurable |
| Available since version | 2.0 |
| Source Code | https://github.com/yiisoft/yii2-httpclient/blob/master/Request.php |
Request represents HTTP request.
Public Properties
| Property | Type | Description | Defined By |
|---|---|---|---|
| $behaviors | yii\base\Behavior[] | List of behaviors attached to this component | yii\base\Component |
| $client | yii\httpclient\Client | Owner client instance. | yii\httpclient\Message |
| $content | string | Raw content. | yii\httpclient\Message |
| $cookies | yii\web\CookieCollection|yii\web\Cookie[]|array | Cookie collection or cookies list. | yii\httpclient\Message |
| $data | mixed | Content data fields. | yii\httpclient\Request |
| $format | string | Body format name. | yii\httpclient\Message |
| $fullUrl | string | Full target URL. | yii\httpclient\Request |
| $headers | array|yii\web\HeaderCollection | Headers collection or headers list in format: [headerName => headerValue] | yii\httpclient\Message |
| $method | string | Request method | yii\httpclient\Request |
| $options | array | Request options. | yii\httpclient\Request |
| $outputFile | resource | yii\httpclient\Request | |
| $url | string|array | Use a string to represent a URL (e.g. `http://some-domain. | yii\httpclient\Request |
Public Methods
| Method | Description | Defined By |
|---|---|---|
| __call() | Calls the named method which is not a class method. | yii\base\Component |
| __clone() | This method is called after the object is created by cloning an existing one. | yii\base\Component |
| __construct() | Constructor. | yii\base\BaseObject |
| __get() | Returns the value of a component property. | yii\base\Component |
| __isset() | Checks if a property is set, i.e. defined and not null. | yii\base\Component |
| __set() | Sets the value of a component property. | yii\base\Component |
| __toString() | PHP magic method that returns the string representation of this object. | yii\httpclient\Message |
| __unset() | Sets a component property to be null. | yii\base\Component |
| addContent() | Adds a content part for multi-part content request. | yii\httpclient\Request |
| addCookies() | Adds more cookies to the already defined ones. | yii\httpclient\Message |
| addData() | Adds data fields to the existing ones. | yii\httpclient\Request |
| addFile() | Adds a file for upload as multi-part content. | yii\httpclient\Request |
| addFileContent() | Adds a string as a file upload. | yii\httpclient\Request |
| addHeaders() | Adds more headers to the already defined ones. | yii\httpclient\Message |
| addOptions() | Adds more options to already defined ones. | yii\httpclient\Request |
| afterSend() | This method is invoked right after this request is sent. | yii\httpclient\Request |
| attachBehavior() | Attaches a behavior to this component. | yii\base\Component |
| attachBehaviors() | Attaches a list of behaviors to the component. | yii\base\Component |
| beforeSend() | This method is invoked right before this request is sent. | yii\httpclient\Request |
| behaviors() | Returns a list of behaviors that this component should behave as. | yii\base\Component |
| canGetProperty() | Returns a value indicating whether a property can be read. | yii\base\Component |
| canSetProperty() | Returns a value indicating whether a property can be set. | yii\base\Component |
| className() | Returns the fully qualified name of this class. | yii\base\BaseObject |
| composeHeaderLines() | Composes raw header lines from $headers. | yii\httpclient\Request |
| detachBehavior() | Detaches a behavior from the component. | yii\base\Component |
| detachBehaviors() | Detaches all behaviors from the component. | yii\base\Component |
| ensureBehaviors() | Makes sure that the behaviors declared in behaviors() are attached to this component. | yii\base\Component |
| getBehavior() | Returns the named behavior object. | yii\base\Component |
| getBehaviors() | Returns all behaviors attached to this component. | yii\base\Component |
| getContent() | Returns HTTP message raw content. | yii\httpclient\Message |
| getCookies() | Returns the cookie collection. | yii\httpclient\Message |
| getData() | Returns the data fields, parsed from raw content. | yii\httpclient\Message |
| getFormat() | Returns body format. | yii\httpclient\Message |
| getFullUrl() | Returns full target URL, including yii\httpclient\Client::$baseUrl as a string. | yii\httpclient\Request |
| getHeaders() | Returns the header collection. | yii\httpclient\Message |
| getMethod() | yii\httpclient\Request | |
| getOptions() | yii\httpclient\Request | |
| getOutputFile() | Gets the outputFile property | yii\httpclient\Request |
| getUrl() | Returns target URL. | yii\httpclient\Request |
| hasContent() | Checks if content with provided name exists | yii\httpclient\Message |
| hasCookies() | Checks of HTTP message contains any cookie. | yii\httpclient\Message |
| hasEventHandlers() | Returns a value indicating whether there is any handler attached to the named event. | yii\base\Component |
| hasHeaders() | Checks of HTTP message contains any header. | yii\httpclient\Message |
| hasMethod() | Returns a value indicating whether a method is defined. | yii\base\Component |
| hasProperty() | Returns a value indicating whether a property is defined for this component. | yii\base\Component |
| init() | Initializes the object. | yii\base\BaseObject |
| off() | Detaches an existing event handler from this component. | yii\base\Component |
| on() | Attaches an event handler to an event. | yii\base\Component |
| prepare() | Prepares this request instance for sending. | yii\httpclient\Request |
| send() | Sends this request. | yii\httpclient\Request |
| setContent() | Sets the HTTP message raw content. | yii\httpclient\Message |
| setCookies() | Sets the cookies associated with HTTP message. | yii\httpclient\Message |
| setData() | Sets the data fields, which composes message content. | yii\httpclient\Request |
| setFormat() | Sets body format. | yii\httpclient\Message |
| setFullUrl() | Sets full target URL. | yii\httpclient\Request |
| setHeaders() | Sets the HTTP headers associated with HTTP message. | yii\httpclient\Message |
| setMethod() | yii\httpclient\Request | |
| setOptions() | Following options are supported: - timeout: int, the maximum number of seconds to allow request to be executed. | yii\httpclient\Request |
| setOutputFile() | Used with yii\httpclient\CurlTransport to set the file that the transfer should be written to | yii\httpclient\Request |
| setUrl() | Sets target URL. | yii\httpclient\Request |
| toString() | Returns string representation of this HTTP message. | yii\httpclient\Request |
| trigger() | Triggers an event. | yii\base\Component |
Protected Methods
| Method | Description | Defined By |
|---|---|---|
| defaultFormat() | Returns default format name. | yii\httpclient\Message |
Events
| Event | Type | Description | Defined By |
|---|---|---|---|
| EVENT_AFTER_SEND | yii\httpclient\RequestEvent | An event raised right after request has been sent. | yii\httpclient\Request |
| EVENT_BEFORE_SEND | yii\httpclient\RequestEvent | An event raised right before sending request. | yii\httpclient\Request |
Property Details
Content data fields.
Full target URL.
Request method
Request options.
Use a string to represent a URL (e.g. http://some-domain.com
, item/list
),
or an array to represent a URL with query parameters (e.g. ['item/list', 'param1' => 'value1']
).
Method Details
Adds a content part for multi-part content request.
| public $this addContent ( $name, $content, $options = [] ) | ||
| $name | string | Part (form input) name. |
| $content | string | Content. |
| $options | array | Content part options, valid options are:
|
| return | $this | Self reference. |
|---|
Adds data fields to the existing ones.
| public $this addData ( $data ) | ||
| $data | array | Additional content data fields. |
| return | $this | Self reference. |
|---|
Adds a file for upload as multi-part content.
See also addContent().
| public $this addFile ( $name, $fileName, $options = [] ) | ||
| $name | string | Part (form input) name |
| $fileName | string | Full name of the source file. |
| $options | array | Content part options, valid options are:
|
| throws | yii\base\InvalidConfigException |
|---|
Adds a string as a file upload.
See also addContent().
| public $this addFileContent ( $name, $content, $options = [] ) | ||
| $name | string | Part (form input) name |
| $content | string | File content. |
| $options | array | Content part options, valid options are:
|
Adds more options to already defined ones.
Please refer to setOptions() on how to specify options.
| public $this addOptions ( array $options ) | ||
| $options | array | Additional options |
| return | $this | Self reference. |
|---|
This method is invoked right after this request is sent.
The method will invoke yii\httpclient\Client::afterSend() and trigger the EVENT_AFTER_SEND event.
| public void afterSend ( $response ) | ||
| $response | yii\httpclient\Response | Received response instance. |
This method is invoked right before this request is sent.
The method will invoke yii\httpclient\Client::beforeSend() and trigger the EVENT_BEFORE_SEND event.
| public void beforeSend ( ) |
Composes raw header lines from $headers.
Each line will be a string in format: 'header-name: value'.
| public array composeHeaderLines ( ) | ||
| return | array | Raw header lines. |
|---|
Returns full target URL, including yii\httpclient\Client::$baseUrl as a string.
| public string getFullUrl ( ) | ||
| return | string | Full target URL. |
|---|
| public string getMethod ( ) | ||
| return | string | Request method |
|---|
| public array getOptions ( ) | ||
| return | array | Request options. |
|---|
Gets the outputFile property
| public resource getOutputFile ( ) |
Returns target URL.
| public string|array getUrl ( ) | ||
| return | string|array | Target URL or URL parameters |
|---|
Prepares this request instance for sending.
This method should be invoked by transport before sending a request. Do not call this method unless you know what you are doing.
| public $this prepare ( ) | ||
| return | $this | Self reference. |
|---|
Sends this request.
| public yii\httpclient\Response send ( ) | ||
| return | yii\httpclient\Response | Response instance. |
|---|---|---|
| throws | yii\httpclient\Exception |
Sets the data fields, which composes message content.
| public $this setData ( $data ) | ||
| $data | mixed | Content data fields. |
| return | $this | Self reference. |
|---|
Sets full target URL.
This method can be used during request formatting and preparation. Do not use it for the target URL specification, use setUrl() instead.
| public $this setFullUrl ( $fullUrl ) | ||
| $fullUrl | string | Full target URL. |
| return | $this | Self reference. |
|---|
| public $this setMethod ( $method ) | ||
| $method | string | Request method |
| return | $this | Self reference. |
|---|
Following options are supported: - timeout: int, the maximum number of seconds to allow request to be executed.
- proxy: string, URI specifying address of proxy server. (e.g. tcp://proxy.example.com:5100).
- userAgent: string, the contents of the "User-Agent: " header to be used in a HTTP request.
- followLocation: bool, whether to follow any "Location: " header that the server sends as part of the HTTP header.
- maxRedirects: int, the max number of redirects to follow.
- protocolVersion: float|string, HTTP protocol version.
- sslVerifyPeer: bool, whether verification of the peer's certificate should be performed.
- sslCafile: string, location of Certificate Authority file on local filesystem which should be used with the 'sslVerifyPeer' option to authenticate the identity of the remote peer.
- sslCapath: string, a directory that holds multiple CA certificates.
You may set options using keys, which are specific to particular transport, like [CURLOPT_VERBOSE => true]
in case
there is a necessity for it.
| public $this setOptions ( array $options ) | ||
| $options | array | Request options. |
| return | $this | Self reference. |
|---|
Used with yii\httpclient\CurlTransport to set the file that the transfer should be written to
See also \yii\httpclient\CURLOPT_FILE.
| public $this setOutputFile ( $file ) | ||
| $file | resource | |
| return | $this | Self reference. |
|---|
Sets target URL.
| public $this setUrl ( $url ) | ||
| $url | string|array | Use a string to represent a URL (e.g. |
| return | $this | Self reference. |
|---|
Returns string representation of this HTTP message.
| public string toString ( ) | ||
| return | string | The string representation of this HTTP message. |
|---|
Event Details
An event raised right after request has been sent.
An event raised right before sending request.


Page not found
The page you requested could not be found. Try using the navigation or search to find what you're looking for or go to this site's home page.
The page you requested could not be found. Try using the navigation or search to find what you're looking for or go to this site's home page.


--- layout: post title: "British Police Don't Know Difference Between MP3 Player and Gun" date: 2008-02-13 19:27:28 +0000 permalink: /2008/02/13/british-police-dont-know-difference-between-mp3-player-and-gun/ category: Misc redirect_from: - /blog/british-police-dont-know-difference-between-mp3-player-and-gun/ ---
[Normally, I stay away from politics on this blog, but this one is just over the top]
It seems that the British were taking notes when they invaded Germany in the 1940s -- it's time to throw civil liberties to the wind and throw people in jail for nothing, just in case they might try something later.  Additionally, once they realized they had made fools of themselves, they couldn't even offer a proper apology. Oh, and in case anyone was missing it, they tracked him on CCTV cameras the whole way. It wouldn't quite be a police state if we couldn't watch everyone at every second, now would it?


CSS Radio Buttons and Checkboxes: Custom icon
Checkboxes and radio buttons with a custom tick icon: Pure CSS.
Uses Font Awesome for demo.
Radio Buttons
First Choice
Second Choice
Third Choice
Checkboxes
First Choice
Second Choice
Third Choice


graph TB;
A[Do you have a problem in your life?]
B[Then don't worry]
C[Can you do something about it?]
A--no-->B;
A--yes-->C;
C--no-->B;
C--yes-->B;
You need set mermaid: true
in the _config.yml or the markdown’s front matter to enable it.
Generation of diagrams and flowcharts from text in a similar manner as markdown.
Ever wanted to simplify documentation and avoid heavy tools like Visio when explaining your code?
This is why mermaid was born, a simple markdown-like script language for generating charts from text via javascript.
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;
markdown:
```mermaid
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;
```
sequenceDiagram
participant Alice
participant Bob
Alice->John: Hello John, how are you?
loop Healthcheck
John->John: Fight against hypochondria
end
Note right of John: Rational thoughts <br/>prevail...
John-->Alice: Great!
John->Bob: How about you?
Bob-->John: Jolly good!
Documentation for Sequence Diagram
markdown:
```mermaid
sequenceDiagram
participant Alice
participant Bob
Alice->John: Hello John, how are you?
loop Healthcheck
John->John: Fight against hypochondria
end
Note right of John: Rational thoughts <br/>prevail...
John-->Alice: Great!
John->Bob: How about you?
Bob-->John: Jolly good!
```
gantt
dateFormat YYYY-MM-DD
title Adding GANTT diagram functionality to mermaid
section A section
Completed task :done, des1, 2014-01-06,2014-01-08
Active task :active, des2, 2014-01-09, 3d
Future task : des3, after des2, 5d
Future task2 : des4, after des3, 5d
section Critical tasks
Completed task in the critical line :crit, done, 2014-01-06,24h
Implement parser and jison :crit, done, after des1, 2d
Create tests for parser :crit, active, 3d
Future task in critical line :crit, 5d
Create tests for renderer :2d
Add to mermaid :1d
Documentation for Gant Diagram
markdown:
```mermaid
gantt
dateFormat YYYY-MM-DD
title Adding GANTT diagram functionality to mermaid
section A section
Completed task :done, des1, 2014-01-06,2014-01-08
Active task :active, des2, 2014-01-09, 3d
Future task : des3, after des2, 5d
Future task2 : des4, after des3, 5d
section Critical tasks
Completed task in the critical line :crit, done, 2014-01-06,24h
Implement parser and jison :crit, done, after des1, 2d
Create tests for parser :crit, active, 3d
Future task in critical line :crit, 5d
Create tests for renderer :2d
Add to mermaid
```


OAuth 2.0 overview
The OAuth authorization framework allows a third-party
Subscriber
application to obtain limited access to the
Provider
's HTTP service.


Conte makes Barça's Arturo Vidal his No.1 objective for Inter's midfield
The two worked together at Juventus and maintain a great relationship to this day
by Sport.esInter Milan coach Antonio Conte is very interested in two FC Barcelona players: Arturo Vidal and Ivan Rakitic. But according to La Gazzetta dello Sport on Friday, the No.1 objective in January is the Chilean, not the Croatian.
The ex-Chelsea boss wants to strengthen his squad in the winter and Vidal, who he coached at Juventus, fits the profile he wants. a physical, all-action midfielder who has character and can contribute in the final third. Conte is also after a wing-back who can play on either flank (Darmian is the preference) and a forward with similar characteristics to Romelu Lukaku.
However, Inter are not ready to pay big fees and in principle will look for loan deals with an option to buy. In this sense, the option of including midfielder Sensi in some way -- he is liked by Barcelona -- could ease negotiations.
It's still early, though, to say if Conte's wish will become a reality. Vidal is Ernesto Valverde's fourth-choice central midfielder at Barça and his role in the team continues to grow, as could be seen against Real Valladolid when he scored via a brilliant Lionel Messi assist.


LEGEND 1
There are no special containers for legends. Just add an 'as-box' element to an 'as-panel__element'
LEGEND 2
There are no special containers for legends. Just add an 'as-box' element to an 'as-panel__element'
LEGEND 1
There are no special containers for legends. Just add an 'as-box' element to an 'as-panel__element'
LEGEND 2
There are no special containers for legends. Just add an 'as-box' element to an 'as-panel__element'


Faculty homework. Word sense disambiguation using wordnet and Banerjee and Pedersen algorithm
Keyword:
Enter text:
OK
Output:
Students
Chichirita Ciprian
Penariu Patricia
Gavrila Anelusa


M
Time
Sun&Rain
Love
Run
Ii, by miracle, can be, This live-long minute true to thee, 'Tis all that heaven allows.


To Do Example
Name:
Name cannot be empty
Email:
Email contains an @
Website:
Website must start with http://
Message:
Message cannot be empty


{% trans %} Flicks has been walking the red carpet this summer at the New Horizons and Cinemalaya film festivals. Catch up with our official recap. {% endtrans %}
{{ _('Read the blog post') }} * {{ _('English only') }}


darkhistory.physics¶
Physics functions as well as constants.
Throughout DarkHistory, we choose cm, s and eV as our system of units. Masses and temperatures are also given in eV. Particle Data Group central values [1] are used for constants, while cosmological parameters are set to the central values of the Planck 2018 baseline TT,TE,EE+lowE+lensing [2].
Fundamental Constants¶
Attributes
mp |
Proton mass in eV. |
me |
Electron mass in eV. |
mHe |
Helium nucleus mass in eV. |
hbar |
hbar in eV s. |
c |
Speed of light in cm s-1. |
kB |
Boltzmann constant in eV K-1. |
alpha |
Fine structure constant. |
ele |
Electron charge in coulombs. |
mass |
Masses of Standard Model particles. |
thomson_xsec |
Thomson cross section in cm2. |
stefboltz |
Stefan-Boltzmann constant in eV-3 cm-2 s-1. |
ele_rad |
Classical electron radius in cm. |
ele_compton |
Electron Compton wavelength in cm. |
Cosmology¶
Attributes
h |
h parameter. |
H0 |
Hubble parameter today in s-1. |
omega_m |
Omega of all matter today. |
omega_rad |
Omega of radiation today. |
omega_lambda |
Omega of dark energy today. |
omega_baryon |
Omega of baryons today. |
omega_DM |
Omega of dark matter today. |
rho_crit |
Critical density of the universe in eV cm-3. |
rho_DM |
DM density in eV cm-3. |
rho_baryon |
Baryon density in eV cm-3. |
nB |
Baryon number density in eV cm-3. |
nH |
Atomic hydrogen number density in cm-3. |
nHe |
Atomic helium number density in cm-3. |
nA |
Hydrogen and helium number density in cm-3. |
chi |
Ratio of helium to hydrogen nuclei. |
YHe |
Helium abundance by mass. |
Functions
hubble (rs[, H0, omega_m, omega_rad, …]) |
Hubble parameter in s-1. |
dtdz (rs[, H0, omega_m, omega_rad, omega_lambda]) |
dt/dz in s. |
TCMB (rs) |
CMB temperature in eV. |
CMB_N_density (T) |
CMB number density in cm-3. |
CMB_eng_density (T) |
CMB energy density in eV cm-3. |
CMB_spec (eng, temp) |
CMB spectrum in number of photons cm-3 eV-1. |
Tm_std (rs) |
Baseline Tm value. |
xHII_std (rs) |
Baseline nHII/nH value. |
xHeII_std (rs) |
Baseline nHeII/nH value. |
get_optical_depth (rs_vec, xe_vec) |
Computes the optical depth given an ionization history. |
inj_rate (inj_type, rs[, mDM, sigmav, lifetime]) |
Dark matter annihilation/decay energy injection rate. |
struct_boost_func ([model, model_params]) |
Structure formation boost factor 1+B(z). |
Atomic and Optical Physics¶
Attributes
rydberg |
Ionization potential of ground state hydrogen in eV. |
lya_eng |
Lyman alpha transition energy in eV. |
lya_freq |
Lyman alpha transition frequency in Hz. |
width_2s1s_H |
Hydrogen 2s to 1s decay width in s-1. |
bohr_rad |
Bohr radius in cm. |
He_ion_eng |
Energy needed to singly ionize neutral He in eV. |
He_exc_lambda |
HeI n=1 to n=2 excitation wavelength in cm. |
He_exc_eng |
HeI n=1 to n=2 excitation energies in eV. |
A_He_21p |
Einstein coefficient for 21p \(\to\) 1s decay in s-1. |
A_He_23P1 |
Einstein coefficient for 23P1 \(\to\) 1s decay in s-1. |
width_21s_1s_He |
Width of He 21s \(\to\) 1s decay in s-1. |
Functions
alpha_recomb (T_m, species) |
Case-B recombination coefficient. |
beta_ion (T_rad, species) |
Case-B photoionization coefficient. |
peebles_C (xHII, rs) |
Hydrogen Peebles C coefficient. |
C_He (xHII, xHeII, rs, species) |
Helium C coefficients. |
xe_Saha (rs, species) |
Saha equilibrium ionization value for H and He. |
d_xe_Saha_dz (rs, species) |
z-derivative of the Saha equilibrium ionization value. |
photo_ion_rate (rs, eng, xH, xe[, atom]) |
Photoionization rate in cm-3 s-1. |
photo_ion_xsec (eng, species) |
Photoionization cross section in cm2. |
coll_exc_xsec (eng[, species]) |
e-e collisional excitation cross section in cm2. |
coll_ion_sec_elec_spec (in_eng, eng[, species]) |
Secondary electron spectrum after collisional ionization. |
coll_ion_xsec (eng[, species]) |
e-e collisional ionization cross section in cm2. |
elec_heating_engloss_rate (eng, xe, rs) |
Electron energy loss rate of electrons due to Coulomb heating in eV s-1. |
Footnotes
| [1] |
|
| [2] | Tanabashi et al. (Particle Data Group), Phys. Rev. D 98, 030001 (2018). |


Warehouse Keeper Holvas:
This warehouse is as safe as our long experience and unique technology can make it. Why, we've never lost so much as a single Adena!
Private Warehouse
Clan Warehouse
Learn skills.
Quest


pslatex(1) teTeX pslatex(1) NAME pslatex - utility to typeset LaTeX files using PostScript fonts SYNOPSIS pslatex [LATEXARGS] LATEXFILE[.tex] DESCRIPTION pslatex allows you to typeset a LaTeX source file using basic Adobe Type 1 PostScript fonts (Times, Helvetica, and Courier) without editing the file to load the necessary packages. It takes any arguments that latex(1) can take. OPTIONS None. FILES Many. See the readme file for pslatex.sty. SEE ALSO latex(1), TEXMF/latex/pslatex/00readme.txt BUGS None known. Report any found to the author. AUTHOR pslatex was written by David Carlisle<EMAIL_ADDRESS>This manual page was written by C.M. Connelly<EMAIL_ADDRESS>for the Debian GNU/Linux system. It may be used by other distributions without contacting the author. Any mistakes or omissions in the manual page are my fault; inquiries about or corrections to this manual page should be directed to me (and not to the primary author). teTeX September 2000 pslatex(1)