mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-09-23 01:25:32 +00:00
Xcode
autoconf
bindings
cmake
docs
examples
include
lib
projects
runtime
test
tools
unittests
utils
PerfectShuffle
TableGen
buildit
emacs
README
emacs.el
llvm-mode.el
tablegen-mode.el
fpcmp
jedit
lint
unittest
vim
DSAclean.py
DSAextract.py
GenLibDeps.pl
Makefile
NLT.schema
NewNightlyTest.pl
NightlyTest.gnuplot
NightlyTestTemplate.html
OldenDataRecover.pl
RegressionFinder.pl
cgiplotNLT.pl
check-each-file
codegen-diff
countloc.sh
findmisopt
findoptdiff
findsym.pl
getsrcs.sh
importNLT.pl
llvm-native-gcc
llvm-native-gxx
llvm.grm
llvmdo
llvmgrep
makellvm
mkpatch
parseNLT.pl
plotNLT.pl
profile.pl
userloc.pl
webNLT.pl
website
win32
CMakeLists.txt
CREDITS.TXT
LICENSE.TXT
Makefile
Makefile.common
Makefile.config.in
Makefile.rules
ModuleInfo.txt
README.txt
build-for-llvm-top.sh
configure
llvm.spec.in
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
-*- llvm/utils/emacs/README -*- These are syntax highlighting files for the Emacs and XEmacs editors. Included are: * llvm-mode.el Syntax highlighting mode for LLVM assembly files. To use, add this code to your ~/.emacs : (setq load-path (cons (expand-file-name "path-to-llvm/utils/emacs") load-path)) (require 'llvm-mode) * tablegen-mode.el Syntax highlighting mode for TableGen description files. To use, add this code to your ~/.emacs: (setq load-path (cons (expand-file-name "path-to-llvm/utils/emacs") load-path)) (require 'tablegen-mode) Note: If you notice missing or incorrect syntax highlighting, please contact <llvmbugs [at] cs.uiuc.edu>; if you wish to provide a patch to improve the functionality, it will be most appreciated. Thank you.