summaryrefslogtreecommitdiffstats
path: root/llvm/examples/HowToUseJIT/HowToUseJIT.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2012-01-25 07:40:15 +0000
committerChandler Carruth <chandlerc@gmail.com>2012-01-25 07:40:15 +0000
commit44d69d9c25dd6215332f240b9c475e70e81a3e2c (patch)
treed0987127a2e3327afc633e6c60095140b926239f /llvm/examples/HowToUseJIT/HowToUseJIT.cpp
parentef6a2ea2163061e7a97dfe3d446b33bb5cc1b3dd (diff)
downloadbcm5719-llvm-44d69d9c25dd6215332f240b9c475e70e81a3e2c.tar.gz
bcm5719-llvm-44d69d9c25dd6215332f240b9c475e70e81a3e2c.zip
Revert a tiny bit of r148553 which extended LLVM's function attributes
to 64-bits, and added a new attribute in bit #32. Specifically, remove this new attribute from the enum used in the C API. It's not yet clear what the best approach is for exposing these new attributes in the C API, and several different proposals are on the table. Until then, we can simply not expose this bit in the API at all. Also, I've reverted a somewhat unrelated change in the same revision which switched from "1 << 31" to "1U << 31" for the top enum. While "1 << 31" is technically undefined behavior, implementations DTRT here. However, MS and -pedantic mode warn about non-'int' type enumerator values. If folks feel strongly about this I can put the 'U' back in, but it seemed best to wait for the proper solution. llvm-svn: 148937
Diffstat (limited to 'llvm/examples/HowToUseJIT/HowToUseJIT.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud