Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Fix for non-standard variable length array"
2004 Oct 18
0
[LLVMdev] Fix for non-standard variable length array
There was a similar problem some time ago, and was resolved with
alloca. I think it's a better solution to use the stack instead of the
heap...
---
Paolo Invernizzi
On Oct 18, 2004, at 3:12 PM, Morten Ofstad wrote:
> In lib/CodeGen/LiveVariables.cpp a variable length array is created.
> Since this is not standard C++, it won't compile with Visual Studio
> (for interested
2004 Oct 18
2
[LLVMdev] Fix for non-standard variable length array
> There was a similar problem some time ago, and was resolved with alloca.
> I think it's a better solution to use the stack instead of the heap...
Actually, I looked into this and alloca is not standard C++ since it can
create problems for the exception handling (although it compiles fine
with Visual C). This is probably why there have been compilation
problems on some platforms
2004 Oct 18
3
[LLVMdev] Fix for non-standard variable length array
Paolo Invernizzi wrote:
> I submitted a patch with a std::vector, but was commited as alloca ;-P
for the other problem?
I made a nice clean patch using std::vector in LiveVariables.cpp now,
which I include with this message... By the way, where do you submit the
patches if not to the mailing list? I thought I should post here so
Paolo and others interested in the porting effort can apply
2004 Oct 18
0
[LLVMdev] Fix for non-standard variable length array
I submitted a patch with a std::vector, but was commited as alloca ;-P
---
P
On Oct 18, 2004, at 4:04 PM, Morten Ofstad wrote:
>> There was a similar problem some time ago, and was resolved with
>> alloca. I think it's a better solution to use the stack instead of
>> the heap...
>
> Actually, I looked into this and alloca is not standard C++ since it
> can
2004 Oct 18
2
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
Chris Lattner wrote:
>>>Can you explain what goes wrong without the stub? It's the only part that
>>>I didn't apply.
>>
>>The X86 backend doesn't get registered since there are no references to
>>symbols in X86TargetMachine the object file is never pulled in from the
>>library I create, and thus the static intializer for the RegisterTarget
2004 Oct 18
3
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
Paolo Invernizzi wrote:
> There was a similar problem some time ago, and was resolved with alloca.
> I think it's a better solution to use the stack instead of the heap...
I tend to agree, but the constructors won't get called if it's an object
array -- anyway, this particular case there was no objects, just
pointers and bools so alloca should be fine. I'll leave it to
2004 Oct 18
0
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
On Mon, 18 Oct 2004, Morten Ofstad wrote:
> > I'm not sure how your patch fixes it though. The only references added by
> > your change would be within the X86 library. How does this change the
> > situation?
>
> Because I'm including the X86TargetMachine header from the application
> (Fibonacci.cpp) .. I know, I know -- but really, I tried everything to
>
2004 Oct 18
0
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
On Mon, 18 Oct 2004, Morten Ofstad wrote:
> Chris Lattner wrote:
> > Can you explain what goes wrong without the stub? It's the only part that
> > I didn't apply.
>
> The X86 backend doesn't get registered since there are no references to
> symbols in X86TargetMachine the object file is never pulled in from the
> library I create, and thus the static
2004 Oct 18
3
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
Chris Lattner wrote:
> Can you explain what goes wrong without the stub? It's the only part that
> I didn't apply.
The X86 backend doesn't get registered since there are no references to
symbols in X86TargetMachine the object file is never pulled in from the
library I create, and thus the static intializer for the RegisterTarget
is never called...
2004 Sep 25
2
[LLVMdev] Sconstruct for win32
Here is the pre-pre-pre alpha of the file, llease be kind <g>
I give up on TableGen... cannot build the flex/bison emitted files ;-(
With my hacked version of the checkout the script build Fibonacci.exe
and HowToUseJIT.exe among with the proper libraries.
I included also a demo version of the HowToUseJIT Visual studio project
generated by the script.
You can debug the program in the
2011 Aug 15
0
[LLVMdev] LLVM 2.9 64bits on Visual Studio 9
FYI, I have confirmed it works on VS10SP1 with x64|Release.
E:\llvm\build\cmake-x64-vs10>bin\Release\Fibonacci.exe 24
verifying... OK
We just constructed this LLVM module:
---------
; ModuleID = 'test'
(snip)
---------
starting fibonacci(24) with JIT...
Result: 46368
...Takumi
2011/8/11 <gleizesd at gmail.com>:
> Hello everybody,
>
> I have sucessfully compiled LLVM
2011 Aug 11
2
[LLVMdev] LLVM 2.9 64bits on Visual Studio 9
Hello everybody,
I have sucessfully compiled LLVM with CMAKE generator "Visual Studio 9 2008
Win64" (OS Windows 7).
-But when I run the Fibonacci example program in "release" mode, I get a
crash with this visual studio popup message :
Microsoft Visual Studio C Runtime Library has detected a fatal error in
Fibonacci.exe.
-Here is the visual studio output:
2007 Jul 14
1
[LLVMdev] JIT Leaks?
Hi all,
I'm playing with the JIT trying to find out the best way to handle a
genetic algorithm that we are developing: I need to:
1) generate about 50.000 functions a time
2) JIT them and execute them over a large dataset
3) Discard everything
4) ... stuff...
5) Loop to 1 again and again and again...
I've the code running, under LLVM 2.0 on OS X 10.4.10 but it leaks,
so I started to
2018 May 30
0
[SROA][DebugInfo][GSoC] Testing SROA on amalgamated sqlite source
>
>
> `SROA' is an early stage pass running at the very beginning of the
> pipeline in `-O{1,2,3}'. Greg Bedwell's report from his DExTer tool
> shows SROA on function as one of the major culprits of Debug Info
> loss.
>
>
The methodology I used is with the opt-bisect-limit option on clang, so
it's not strictly the case that the results presented
2007 Sep 05
2
[LLVMdev] Seeing a crash with ConstantFP::get
Hola LLVMers,
I'm getting a crash when using ConstantFP::get.
I can repro it by adding one line to the Fibonacci example program:
int main(int argc, char **argv) {
int n = argc > 1 ? atol(argv[1]) : 24;
// Create some module to put our function into it.
Module *M = new Module("test");
// We are about to create the "fib" function:
Function
2011 Apr 20
5
Fibonacci
Hi!
I am trying to work out the code to get a Fibonacci sequence, using the
while() loop and only one variable. And I can't figure it out.
Fibonacci<-c(1,1)
while (max(Fibonacci)<500){
Fibonacci<-c(Fibonacci, (max(Fibonacci) + ?(Fibanacci)))
}
How can I tell R to take the value one before the max value? (Without
defining another variable)
(Probably super easy... I am a
2007 Sep 05
0
[LLVMdev] Seeing a crash with ConstantFP::get
On Sep 5, 2007, at 2:21 PM, Chuck Rose III wrote:
> Hola LLVMers,
>
>
>
> I’m getting a crash when using ConstantFP::get.
>
>
>
> I can repro it by adding one line to the Fibonacci example program:
>
>
>
> int main(int argc, char **argv) {
>
> int n = argc > 1 ? atol(argv[1]) : 24;
>
>
>
> // Create some module to put our function
2004 Feb 03
3
Implementating streams in R
Dear all,
I have an implementation of streams in R. The current implementation of
delay() and force() is
inspired from the LISP implementation found in Part VI "Languages for AI
problem solving" of
"Artificial Intelligence" by G. Luger.
I have tested it with the Fibonacci example in the same book (see examples
below). It works
but I do run into a problem when I try to
2007 Sep 05
2
[LLVMdev] Seeing a crash with ConstantFP::get
It's in debug. I'm having a look at the assembler it's producing right
now and it's definitely a little odd for what should be a simple
assignment in zeroSignificand.
________________________________
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On Behalf Of Dale Johannesen
Sent: Wednesday, September 05, 2007 2:39 PM
To: LLVM Developers Mailing
2007 Sep 06
0
[LLVMdev] Seeing a crash with ConstantFP::get
Hola Dale,
I spent some time walking through what's going on with a friend of mine
from VStudio. Category is given 2 bits in the APFloat class definition.
It's sign extending the enum value for the comparisons when it loads it
out of the class, so the 2 becomes a -2 and the comparison fails. He
sent me a piece of code which I might be able to use to force the issue.
I'll update