Displaying 7 results from an estimated 7 matches for "dummy_funct".
Did you mean:
dummyfunct
2007 Jul 13
0
[LLVMdev] llvm-gcc-4-2 development branch is open
...here it came from?
Thanks, Duncan.
@@ -28,6 +28,7 @@
#include "llvm/Bitcode/ReaderWriter.h"
#include "llvm/CodeGen/ScheduleDAG.h"
#include "llvm/CodeGen/Passes.h"
+#include "llvm/Support/MemoryBuffer.h"
#include "llvm/Support/Streams.h"
/// dummy_function - This is used when linking the LLVM libraries into a dynamic
@@ -40,8 +41,10 @@
void dummy_function() {
new llvm::ExistingModuleProvider(0);
llvm::createVerifierPass();
- llvm::WriteBitcodeToFile(0, llvm::cout);
+ llvm::CreateBitcodeWriterPass(*llvm::cout);
+ llvm::WriteBitcodeToFile(...
2015 Nov 02
2
noalias parameter attribute not currently exploited by alias analysis?
...ount(8)
for (i = 0; i < len; i++) {
a = *input_buf++;
b = *input_buf++;
c = *input_buf++;
a = (uint8_t) (a - 10);
b = (uint8_t) (b - 20);
c = (uint8_t) (c - 30);
*output_buf++ = a;
*output_buf++ = b;
*output_buf++ = c;
}
}
__attribute__((flatten))
void dummy_function(int len, uint8_t *input_buf, uint8_t *output_buf) {
printf("This function exists just to examine inlining behaviour\n");
main_loop(len, input_buf, output_buf);
}
Just to skip ahead to my conclusions, as far as I can see:
* In main_loop, the noalias parameter attribute isn't ex...
2007 Jul 13
2
[LLVMdev] llvm-gcc-4-2 development branch is open
...is
> @@ -28,6 +28,7 @@
> #include "llvm/Bitcode/ReaderWriter.h"
> #include "llvm/CodeGen/ScheduleDAG.h"
> #include "llvm/CodeGen/Passes.h"
> +#include "llvm/Support/MemoryBuffer.h"
> #include "llvm/Support/Streams.h"
>
> /// dummy_function - This is used when linking the LLVM libraries into a dynamic
> @@ -40,8 +41,10 @@
> void dummy_function() {
> new llvm::ExistingModuleProvider(0);
> llvm::createVerifierPass();
> - llvm::WriteBitcodeToFile(0, llvm::cout);
> + llvm::CreateBitcodeWriterPass(*llvm::cout);
&...
2007 Jul 14
0
[LLVMdev] llvm-gcc-4-2 development branch is open
...vm-gcc-4.2
today, check llvm-linker-hack.cpp yourself if you like. There was a change
to the mirror in May 07, but it was just changing Bytecode -> Bitcode. My
guess is the Evan's change didn't reach the mirror. Here is the function
as it exists in the llvm-gcc-4.0 mirror today:
void dummy_function() {
new llvm::ExistingModuleProvider(0);
llvm::createVerifierPass();
llvm::WriteBitcodeToFile(0, llvm::cout);
llvm::ParseBitcodeFile(NULL);
...
and in llvm-gcc-4.2:
void dummy_function() {
new llvm::ExistingModuleProvider(0);
llvm::createVerifierPass();
llvm::CreateBitcodeWriterPa...
2007 Jul 13
2
[LLVMdev] llvm-gcc-4-2 development branch is open
On Jul 13, 2007, at 9:28 AM, Duncan Sands wrote:
> Hi Chris,
>
>> This is probably a patch that got checked into llvm-gcc4 after devang
>> started work on 4.2. Please feel free to update 4.2 to the version
>> in
>> 4.0.
>
> no, it doesn't exist in 4.0.
hmm. that can not be true. It was applied by Evan on May 07, 2007 to
unbreak Apple style builds.
-
2017 Dec 11
0
document environment passing in parallel::parLapply
...les unrelated to
the parLapply call. However, this is not clearly documented. Therefore
I would like to suggest expanding the relevant documentation to
explain this behaviour.
Consider this example:
parallel_demo <- function(random_values_count) {
some_data <- runif(random_values_count)
dummy_function <- function(x) {
x
}
cluster <- parallel::makeCluster(3)
start <- proc.time()
parallel::parLapply(cluster, 1:3, dummy_function)
runtime <- proc.time() - start
parallel::stopCluster(cluster)
runtime
}
parallel_demo(10)
parallel_demo(100 * 1000 * 1000)
On my machi...
2007 Jul 11
12
[LLVMdev] llvm-gcc-4-2 development branch is open
Hi All,
llvm-gcc-4-2 development branch is now open for development at
llvm.org/svn/llvm-project/llvm-gcc-4-2
It is not yet ready, it can not even bootstrap. I welcome LLVM
developers to test and apply fixes!
However, first take a note of ground rules :
1) LLVM developers, use your write access as judiciously as you use it
for LLVM development and follow same check-in procedure.
2)