Saving SSE state

Index > Main > Saving SSE state

Goto page Previous 1, 2

Author

Thread

HaHaAnonymous

Joined: 02 Dec 2012
Posts: 1178
Location: Unknown

HaHaAnonymous 26 Feb 2015, 16:17

[ Post removed by author. ]

Last edited by HaHaAnonymous on 28 Feb 2015, 17:51; edited 1 time in total

26 Feb 2015, 16:17

system error

Joined: 01 Sep 2013
Posts: 670

system error 26 Feb 2015, 16:27

revolution wrote:

You need to tell MS about your suggestion. Perhaps they will like it and make a new calling convention and apply it to all string and char routines and then tell everyone to change there C codes for the new convention.

This is not a calling convention issue. It's about what is appropriate and what is not. Its all about common sense. Involving 128-bit and 256-bit wide heavyweight registers just to make a putchar routine is not making any sense at all. Except of course if you are a Miscrosoft lover or fanatic.

26 Feb 2015, 16:27

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20761
Location: In your JS exploiting you and your system

revolution 26 Feb 2015, 16:33

Actually this is all about calling convention. Nothing else. You want a selected set of the APIs to do something different. That means you want to change the calling convention for those APIs.

From what I have seen (although I haven't seen them all) 64-bit APIs use FASTCALL without any exceptions. And I would guess Linux uses its convention also for all APIs. It makes things predicable and easy to remember.

26 Feb 2015, 16:33

system error

Joined: 01 Sep 2013
Posts: 670

system error 26 Feb 2015, 16:34

HaHaAnonymous wrote:

Quote:

but a putchar?? LOL. Its an overkill.

Agreed.

On Linux the write to stdout function (write) does not alter the xmm registers. Assuming that is what putchar does.

Linux has a cleaner design. No doubt about it.

26 Feb 2015, 16:34

system error

Joined: 01 Sep 2013
Posts: 670

system error 26 Feb 2015, 16:39

revolution wrote:

Actually this is all about calling convention. Nothing else. You want a selected set of the APIs to do something different. That means you want to change the calling convention for those APIs.

From what I have seen (although I haven't seen them all) 64-bit APIs use FASTCALL without any exceptions. And I would guess Linux uses its convention also for all APIs. It makes things predicable and easy to remember.

You call it calling convention. I call it inappropriate use of user's resources! That user is us. That resources are ours. not Microsoft.

26 Feb 2015, 16:39

HaHaAnonymous

Joined: 02 Dec 2012
Posts: 1178
Location: Unknown

HaHaAnonymous 26 Feb 2015, 16:57

[ Post removed by author. ]

26 Feb 2015, 16:57

Goto page Previous 1, 2

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum