flat assembler
Message board for the users of flat assembler.
Index
> Main > 256 bit SSE aka AVX Goto page Previous 1, 2, 3, 4, 5 Next |
Author |
|
bitRAKE 07 Apr 2008, 23:14
f0dder wrote: that isn't enough to guard against malware. Doesn't really matter if you have 1023 cores still running, if your system is infected and sending out spam mails _________________ ¯\(°_o)/¯ “languages are not safe - uses can be” Bjarne Stroustrup |
|||
07 Apr 2008, 23:14 |
|
f0dder 07 Apr 2008, 23:30
It's an interesting idea, and I'm sure there's a lot research going on about it. But it would need pretty different architecture than just 1024 x86 cores with some self-healing... like, making sure there's no way the malware could spread to additional cores. And we still have the problems of infected system files etc. - that requires re-thinking some OS concepts.
Trusted Computing could be used for some really nice things, too bad the main reason it's being implemented is for DRM restrictions |
|||
07 Apr 2008, 23:30 |
|
edfed 07 Apr 2008, 23:59
one very interresting data type would the analog signals.
make calculations on analog values ( very, very fast ) , use ADC and DAC to work with in digital x86 mechanism too. delta-sigma is a very good type of ADC, i made some prototypes in my early ages in electronics and t show some very interresting properties. a sort of mix between analog and digital. about malwares, i repeat, don't do malware, it is exactlly the same principle as bad mentality education. have the same destruction effects. to kill and detect malwares, a good theory can be not to build antivir, but more build a good meta code; to control the multiple processes and provide some hardware and transparent process control, watch dog flow control is a good start. it can be of any type: timer, semapkore, checkpoint, boss etc... but the problem is always here... malware coders ( more frustrated childrens or evil based dumbs) shall be stopped and if possible, we shall destroy their machines. one evidence is that i made a sort of virus cause of anger, and some weeks later, i used it and it did what you know. the only copy of this "malware?" is on this forum. it is a simple disk eraser. i made it to verify the ability of the system to localise the sectors reliabily. putting a string on the sectors to tell it's number and then, verify it effectivelly works. our mission as coders is to fight it, not ot expend it. exactlly as the mission of parents is to make a good education for their childrens. if i knew benjamin trojan ( or any virus builder), instead to give him a job, i give him a pair of fists in the face. exactlly as i do for all evil personns who wants to make bad actions. create malwares, ok, it's a part of the knowledge for all coders, but only for tests and defence, and never for bad actions, as in real life about martial arts. there are some laws, the lengendary 3 laws of the robotics. as code are robots without body, it shall respect them. sounds like an utopia, but it is like that, remember that the future is ours and we shall create for a better world, not the opposite. |
|||
07 Apr 2008, 23:59 |
|
revolution 08 Apr 2008, 00:34
Remy Vincent wrote: HELLO revolution, what do you think of this kind of solutions? Indeed letting everyone choose their own opcodes would be complete chaos. |
|||
08 Apr 2008, 00:34 |
|
bitRAKE 08 Apr 2008, 09:17
Too bad the stack machine idea didn't stay mainstream. There really isn't any need to have registers to hold data - they should all be memory pointers to stacks. Either circular like the FPU (but larger than 8 values), or linear like (R|E)SP. 16 configurable stacks should be plenty.
_________________ ¯\(°_o)/¯ “languages are not safe - uses can be” Bjarne Stroustrup |
|||
08 Apr 2008, 09:17 |
|
tom tobias 09 Apr 2008, 17:50
bitRAKE wrote: ...Too bad the stack machine idea didn't stay mainstream. ... revolution wrote:
I think it is very important to offer the user the opportuntity, NO, the obligation, to define many of the operations now performed by intel's architecture. I believe we need at most a dozen native cpu instructions, from which all of the others can be derived, as needed, in each application. What would be useful is a list of the absolute minimum necessary instructions for the cpu to possess.... any thoughts? |
|||
09 Apr 2008, 17:50 |
|
f0dder 09 Apr 2008, 18:01
tom tobias: if you want a machine just for browsing the web and writing emails, "getting rid of instructions" might be doable. But in the real world where we want to do image and sound processing, video compression, and all that - we need fancy stuff like SSE for the performance.
|
|||
09 Apr 2008, 18:01 |
|
bogdanontanu 09 Apr 2008, 18:21
Tom,
It is also my intention to make my own more simple CPU. Maybe we could join efforts. |
|||
09 Apr 2008, 18:21 |
|
edfed 09 Apr 2008, 18:40
bogdanontanu, you that have writen solar os, and have a network dirver, can you lead me to the right datas or tutorials. i need to understand and write them in less than 1 month for the FEEBLE.
this would be the first step to the machine that tom wants still exist and is a old Pentium 100MHz with vesa compliant card like sis6215. then, it would be very possible to have a dedicated machine to internet without any system else than a browser and a client/server. me too i want to build my own simple µP, but i see it is endless as there is an existing X86 platform that is not so hard to use. but it needs a lot of experience, as building a µP need more experience, and not only in assembly or C. create a digital chip is not an easy task. you should consider a lot of physical laws. the time you can make a simpler and as powerfull µP than x86 will be a waste of time that can be used to learn more about the existing. but yes, making a new µP family is not a bad idea. they shall have the same opcodes as x86. Last edited by edfed on 09 Apr 2008, 23:23; edited 1 time in total |
|||
09 Apr 2008, 18:40 |
|
sakeniwefu 09 Apr 2008, 21:00
In the end, all opcodes turn into a handful of uops in current Intels and AMDs, don't they? If we could program in uops directly, performance wouldn't get any worse. Although I heard RISC cpus are a PITA for assembly programmers.
|
|||
09 Apr 2008, 21:00 |
|
revolution 10 Apr 2008, 00:13
sakeniwefu wrote: In the end, all opcodes turn into a handful of uops in current Intels and AMDs, don't they? If we could program in uops directly, performance wouldn't get any worse. sakeniwefu wrote: Although I heard RISC cpus are a PITA for assembly programmers. |
|||
10 Apr 2008, 00:13 |
|
edfed 10 Apr 2008, 00:34
Quote: It is not the RISC thing that makes it ugly, it is the resources (or lack of resources) available that determine whether a particular CPU will be a PITA to write assembly. totaly true. and as said the teacher who maked me discover assembly, Quote: if you want a big amount of memory, a fast and powerfull envirronment to program big electronic applications, don't use an embeded µC, but a PC. PC and computer in general are the better way to have power in digital electronics. |
|||
10 Apr 2008, 00:34 |
|
revolution 10 Apr 2008, 08:39
If you want a TV remote control that won't drain your batteries with a small amount of memory in a small electronic application don't use a PC, but an embeded µC.
|
|||
10 Apr 2008, 08:39 |
|
Madis731 13 Apr 2008, 09:41
Touring taught you about "The Minimal Machine", but is that optimal?
I sometimes love the NOT operator, while I still have the XOR. With boolean you can derive all ANDs from ORs etc., but the shortcuts make your code compact. Same goes for ADD/SUB or MUL/DIV and Signed/Unsigned... |
|||
13 Apr 2008, 09:41 |
|
bitRAKE 13 Apr 2008, 19:11
Does Intel perform simulations to better understand how new instructions will effect software? Or, is this sort of thing more a marketing decision? I find it difficult to believe the later has much influence on such an important decision, but I really don't know.
_________________ ¯\(°_o)/¯ “languages are not safe - uses can be” Bjarne Stroustrup |
|||
13 Apr 2008, 19:11 |
|
revolution 14 Apr 2008, 01:03
bitRAKE wrote: Does Intel perform simulations to better understand how new instructions will effect software? Or, is this sort of thing more a marketing decision? I find it difficult to believe the later has much influence on such an important decision, but I really don't know. |
|||
14 Apr 2008, 01:03 |
|
AlexP 14 Apr 2008, 02:18
:0 Just watch, they're going to spend so much time on the new instructions that at the end of the process, someone's going to go "Hey, wasn't there supposed to be an add instruction in these tables?!"
|
|||
14 Apr 2008, 02:18 |
|
MazeGen 14 Apr 2008, 07:41
revolution wrote:
Good question. I always wondered why Intel keeps supporting NEVER documented SETALC instruction. There must be some good reason, but what is the reason? |
|||
14 Apr 2008, 07:41 |
|
revolution 14 Apr 2008, 09:04
MazeGen wrote: I always wondered why Intel keeps supporting NEVER documented SETALC instruction. There must be some good reason, but what is the reason? |
|||
14 Apr 2008, 09:04 |
|
Goto page Previous 1, 2, 3, 4, 5 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2025, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.