flat assembler
Message board for the users of flat assembler.
![]() Goto page Previous 1, 2, 3, 4, 5, 6, 7, 8 |
Author |
|
Furs
system error wrote: with your OWN calling convention |
|||
![]() |
|
Furs
There's no way to say something better than I did to the pure decayed excrement you spew out which, clearly, is fully technobabble and makes absolutely zero sense.
While not the case, let's use the classic callback example in Windows: the message dispatcher callback. Clearly, such callback must use MS ABI (you don't control its calling convention). It is your function (that's why it's a callback), but you have to use MS ABI in it because it's what Windows expects when calling your "callback function" (and that's a period). So, what happens if you use AVX2 in the message dispatcher and use YMM6 register? Think about it hard. |
|||
![]() |
|
system error
Furs wrote: So, what happens if you use AVX2 in the message dispatcher and use YMM6 register? Think about it hard. Then it has nothing to do with MS ABI. Didn't mentioned it 15 times already? Its all about your own IMAGINARY LIBRARY and your own IMAGINARY CALLING CONVENTIONS that nobody uses. I don't give a horsefcuk about it and I am pretty sure nobody does either. Maybe you can train your dog to use it? HAHAHAHA XD So where's the "expert" patch that you been BIG-MOUTHING ABOUT SINCE PAGE 1 to send to those BRILLIANT GCC developers? Why the sudden lost of "expertise"? Or perhaps it's all about maintaining your "Mr Fake Expert" impressions on this board and nothing more? |
|||
![]() |
|
revolution
system error wrote:
|
|||
![]() |
|
system error
revolution wrote: .You are required to follow the calling convention in use. |
|||
![]() |
|
revolution
Furs already explained that the SSE registers are a subset of YMM, and the calling convention mandates that you preserve certain SSE registers. So you can't arbitrarily decide not to preserve the required registers or you will be sorry.
|
|||
![]() |
|
system error
revolution wrote: Furs already explained that the SSE registers are a subset of YMM, and the calling convention mandates that you preserve certain SSE registers. So you can't arbitrarily decide not to preserve the required registers or you will be sorry. MS 64 calling convention is NOT vectorcall. vectorcall is NOT the standard MS64 calling convention!! Those two are referred by specific names! The fact that he keeps on mentioning MS 64 calling convention while referring to AVX instruction says a lot about his incompetency no matter HOW HARD YOU TRY TO HELP HIM! Nice try!! You two are probably related or lovers or something but no. You can't help an already helpless person! It makes you look funny too! hahahaha xD |
|||
![]() |
|
revolution
AVX instructions use the AVX registers. And, as already mentioned, AVX registers are a superset of the SSE registers. So when using AVX instructions we must take care to preserve the required SSE registers. So you can't arbitrarily decide not to preserve the required registers or you will be sorry. It's all interrelated, you can't escape that by making personal insults and unfounded accusations.
|
|||
![]() |
|
system error
revolution wrote: AVX instructions use the AVX registers. And, as already mentioned, AVX registers are a superset of the SSE registers. So when using AVX instructions we must take care to preserve the required SSE registers. So you can't arbitrarily decide not to preserve the required registers or you will be sorry. It's all interrelated, you can't escape that by making personal insults and unfounded speculations. "superset" is not the correct manufactures term. Better use the term "extension". It goes with the traditions --> EAX is an extension to AX. YMM is extended to ZMM. Using the term "superset" makes you look funnier than Furs' "opcode space"! xD And no. When trolling, correctness is the least of my concern, especially against overconfident response-guaranteed targets. I intimidate, interrogate, undermine, question, influence and create confusions. It's entertaining and educating at the same time! hahahaha xD |
|||
![]() |
|
revolution
system error wrote: "superset" is not the correct manufactures term. Better use the term "extension". It goes with the traditions --> EAX is an extension to AX. YMM is extended to ZMM. Using the term "superset" makes you look funnier than Furs' "opcode space"! xD system error wrote: And no. When trolling, correctness is the least of my concern, especially against overconfident response-guaranteed targets. I intimidate, interrogate, undermine, question, influence and create confusions. It's entertaining and educating at the same time! hahahaha xD ![]() |
|||
![]() |
|
Furs
system error wrote: MS 64 calling convention is NOT vectorcall. Callbacks aren't only in Windows obviously, but we can keep it at that for simplicity. (I know that if I started talking about implementing a DSP plugin relying on a callback protocol that uses MS ABI, you would start with random babbling, not like I haven't already mentioned it -- I mean, even libraries like FLAC rely on callbacks and they use MS ABI since it is *default* for this platform) As for your patch question, I believe that was answered on page 4. You know, no matter how many times you ask something stupid it's not going to become an answer you want. |
|||
![]() |
|
system error
Edit by revolution: post has no informational value
|
|||
![]() |
|
system error
Edit by revolution: More trolling
|
|||
![]() |
|
system error
revolution wrote: Okay, extension, thank you for the information. But I don't think extension is precise enough. Because it can also mean in addition to, rather than contains the original within it. "superset" What??? AVX stands for = Advanced Vector EXTENSION. SSE stands for Streaming SIMD EXTENSION See, if you love defending BIG MOUTH IDIOT, you'll eventually become one. "SUPERSET", my foot! |
|||
![]() |
|
Goto page Previous 1, 2, 3, 4, 5, 6, 7, 8 < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.