llvm/utils/vim, branch release_26http://llvm.orghttps://git.amat.us/llvm/atom/utils/vim?h=release_262009-08-05T16:38:48ZAdd new function attribute keywords to the vim syntax.2009-08-05T16:38:48ZDan Gohmangohman@apple.com2009-08-05T16:38:48Zurn:sha1:b8281ca99237319918389d06ae3561c75ab8b4e3
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@78205 91177308-0d34-0410-b5e6-96231b3b80d8
vim syntax highlighting for inbounds keyword.2009-07-27T21:54:51ZDan Gohmangohman@apple.com2009-07-27T21:54:51Zurn:sha1:d5c947022d7bb0b2bf330998e9c4eff941e0f899
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@77260 91177308-0d34-0410-b5e6-96231b3b80d8
Add new keywords to the vim syntax highlighting.2009-07-22T22:45:50ZDan Gohmangohman@apple.com2009-07-22T22:45:50Zurn:sha1:e02a0aa3c6fb77addbd0ddb573ecc4aebaccc8e0
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@76812 91177308-0d34-0410-b5e6-96231b3b80d8
Add the private keyword to the VIM syntax highlighting.2009-07-17T01:06:53ZDan Gohmangohman@apple.com2009-07-17T01:06:53Zurn:sha1:21de024b909a3f2c8b120dd65bc14efba68f919f
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@76134 91177308-0d34-0410-b5e6-96231b3b80d8
Split the Add, Sub, and Mul instruction opcodes into separate2009-06-04T22:49:04ZDan Gohmangohman@apple.com2009-06-04T22:49:04Zurn:sha1:ae3a0be92e33bc716722aa600983fc1535acb122
integer and floating-point opcodes, introducing
FAdd, FSub, and FMul.
For now, the AsmParser, BitcodeReader, and IRBuilder all preserve
backwards compatability, and the Core LLVM APIs preserve backwards
compatibility for IR producers. Most front-ends won't need to change
immediately.
This implements the first step of the plan outlined here:
http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@72897 91177308-0d34-0410-b5e6-96231b3b80d8
It makes no sense to have a ODR version of common2009-03-11T20:14:15ZDuncan Sandsbaldrick@free.fr2009-03-11T20:14:15Zurn:sha1:4dc2b39bf89d7c87868008ef8a0f807e0419aca6
linkage, so remove it.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@66690 91177308-0d34-0410-b5e6-96231b3b80d8
Remove the one-definition-rule version of extern_weak2009-03-11T08:08:06ZDuncan Sandsbaldrick@free.fr2009-03-11T08:08:06Zurn:sha1:5f4ee1fc5d00ae55c30fa2ce450c69be4c6d6e63
linkage: this linkage type only applies to declarations,
but ODR is only relevant to globals with definitions.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@66650 91177308-0d34-0410-b5e6-96231b3b80d8
Introduce new linkage types linkonce_odr, weak_odr, common_odr2009-03-07T15:45:40ZDuncan Sandsbaldrick@free.fr2009-03-07T15:45:40Zurn:sha1:667d4b8de6dea70195ff12ef39a4deebffa2f5c7
and extern_weak_odr. These are the same as the non-odr versions,
except that they indicate that the global will only be overridden
by an *equivalent* global. In C, a function with weak linkage can
be overridden by a function which behaves completely differently.
This means that IP passes have to skip weak functions, since any
deductions made from the function definition might be wrong, since
the definition could be replaced by something completely different
at link time. This is not allowed in C++, thanks to the ODR
(One-Definition-Rule): if a function is replaced by another at
link-time, then the new function must be the same as the original
function. If a language knows that a function or other global can
only be overridden by an equivalent global, it can give it the
weak_odr linkage type, and the optimizers will understand that it
is alright to make deductions based on the function body. The
code generators on the other hand map weak and weak_odr linkage
to the same thing.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@66339 91177308-0d34-0410-b5e6-96231b3b80d8
Fix a missing word.2009-01-21T21:54:44ZDan Gohmangohman@apple.com2009-01-21T21:54:44Zurn:sha1:748dbc6afb7af114674544f760c6d3209a881161
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@62720 91177308-0d34-0410-b5e6-96231b3b80d8
Versions of VIM included with Intrepid and Leopard at least appear2009-01-21T21:52:42ZDan Gohmangohman@apple.com2009-01-21T21:52:42Zurn:sha1:907532dcbb43cd9e6f406a077604e54c63ded08b
to handle symlinks just fine, so reword the instructions in the
README accordingly.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@62719 91177308-0d34-0410-b5e6-96231b3b80d8