search for: read_from_device

...here are some drivers existing for this system and I'd like to be able to call some functions defined there. But these drivers are using very custom calling convention. I thought that declaring functions like follows could be the most appropriate solution: extern __MySpecialDriverAttribute int read_from_device(int devid, int channel); But for doing this I need to define a custom attribute or a new calling convention. Or do you see any other opportunity? > >> For the time being, I'd suggest defining an "fp register set" > which > >> just aliases the integer register s...

...isting for this system and I'd like to be able to > call some functions defined there. But these drivers are using very > custom calling convention. I thought that declaring functions like > follows could be the most appropriate solution: > > extern __MySpecialDriverAttribute int read_from_device(int devid, int > channel); > > But for doing this I need to define a custom attribute or a new calling > convention. Or do you see any other opportunity? I would suggest following the model of stdcall/fastcall in the windows x86 world. Specifically, this would require modifying llvm-...

On Tue, 10 Oct 2006, Roman Levenstein wrote: >>> such a call instruction? >> >> Why not just make the asm string be "call __fsub64"? > > Well, of course it would be the best solution. But the interesting part > is that I need to generate the machine code directly because for > different reasons use of a system assembler is not an option. As a ok. >

Hi, >> My target supports only f64 at the moment. >> Question: How can I tell LLVM that float is the same as double on my >> target? May be by assigning the same register class to both MVT::f32 ?> and MVT::f64? >Just don't assign a register class for the f32 type. This is what the >X86 backend does when it is in "floating point stack mode". This will