Topics: Computer Architecture, RISC vs CISC. #comp_arch

The differences between RISC and CISC architecture. While CISC use more cycles per instruction, RISC does the opposite, using less cycles per instruction, this can be seen with an example in the article. Although RISC needs more RAM to work, it has more performance, since uses less cycles per instruction and programmers can reuse the values of the last instruction (which couldn't be done in CISC, because the instruction erases the data stored in the registers after using it).

https://cs.stanford.edu/people/eroberts/courses/soco/projects/risc/risccisc/

Topics: Integrated Circuits (IC) Reverse Engineering. #reversing #comp_arch #ic

This is a wiki aimed to IC Reverse Engineering, providing a good approach of how ICs are built and how to reverse them.

http://www.siliconpr0n.org/wiki/doku.php

Topics: Memory Mapped I/O and Isolated I/O. #comp_arch

This article explains the differences between Memory Mapped I/O and Isolated I/O (or Port Mapped I/O). Basically, Isolated I/O provides two buses (Data bus and Address bus) and isolated space for both memory and the IO, they are accessed through specific instructions (eg OUT and IN instructions), the control line indicate which address space the CPU will access. In Memory Mapped I/O, the memory is shared with the I/O and can be used with the common memory instructions (eg MOV), although the memory has less space, this is not a big problem anymore, since the actual CPUs are at least 32-bit.

https://www.geeksforgeeks.org/memory-mapped-i-o-and-isolated-i-o/

Additional information

https://www.bogotobogo.com/Embedded/memory_mapped_io_vs_port_mapped_isolated_io.php

Topics: OS, wiki. #os #comp_arch

This wiki provides information about the creation of Operating Systems.

https://wiki.osdev.org/Main_Page

Topics: GCC Inline Assembly, Assembly. #assembly #c #cpp

Just beautiful. This document is a guide of how to use inline assembly in GCC for ARM architecture, Although i don't know ARM, this doc is really useful, since the syntax GCC uses for inline assembly is complex.

https://www.ic.unicamp.br/~celio/mc404-s2-2015/docs/ARM-GCC-Inline-Assembler-Cookbook.pdf

Topics: GCC Inline Assembly, assembly, C. #assembly #cpp #c

This is the documentation for inline assembly with C or C++. Maybe i'm dumb for not understanding this syntax very well, but i really don't like it, besides that, it uses AT&T syntax. Anyway i have been looking this guide and it shows how to use inline assembly for basic instructions (no operands) and instructions which require operands (registers, immediate values, etc), you can see that in the sections Basic Arm and Extended Arm, respectively. The Constraints section will help you to understand the constraints used when you need to use operands, either input or output operands, or registers.

https://gcc.gnu.org/onlinedocs/gcc/Using-Assembly-Language-with-C.html

This one is useful too.


https://www.ibiblio.org/gferg/ldp/GCC-Inline-Assembly-HOWTO.html

Topics: Hacking roadmap. #hacking #roadmap #ebook

This is a roadmap made by Unk9vvN with a list of tools and requirements for web hacking.

From: https://t.me/CyberSecArticles

Topics: Encoding.

A brief explanation of base64. Useful for implementation with programming.

https://fm4dd.com/programming/base64/base64_algorithm.shtm

Topics: Assembly, Computer Architecture. #assembly #comp_arch #book

Summary: 25 Chapters, 1426 pages.

This ebook has a lot of information about assembly and basic computer architecture.

Topics: Math. #math

This article shows the mathematical aspects of an ocean wave and tsunami.

https://plus.maths.org/content/os/issue34/features/tsunami/index

Additional information.

https://www.compadre.org/osp/EJSS/4032/140.htm

https://en.wikipedia.org/wiki/Group_velocity

Topics: C++, Programming. #cpp

Useful site for C++ learning, it includes tutorials for data structures.

https://www.softwaretestinghelp.com/cpp-tutorials/

Topics: Programming, Data Structures, Math. #programming #math

It's important for programmers to understand which algorithm is more efficient to complete a task, concepts such as Time Complexity (how much time it takes in terms of amount of input to the algorithm), Space Complexity (how much memory it takes in terms of the amount of input to the algorithm) and Big-O Notation are needed for that. Big-O Notation is a notation used to explain the complexity of the algorithm related to an input n, it is about finding the asymptotic upper bound function, that is, the relation of time T(n) and input n as n grows towards infinity.


https://www.cs.utexas.edu/users/djimenez/utsa/cs1723/lecture2.html#:~:text=Time%20complexity%20is%20a%20function,of%20input%20to%20the%20algorithm.&text=Space%20complexity%20is%20a%20function,of%20input%20to%20the%20algorithm.

Additional information.

https://www.freecodecamp.org/news/big-o-notation-why-it-matters-and-why-it-doesnt-1674cfa8a23c/

Topics: Programming. #programming

If you want to improve your programming skills, you can take a look at this list. This wikibook section shows many algorithms and implementations of common problems and techniques of sorting, searching algorithms, hashing, etc.

https://en.m.wikibooks.org/wiki/Algorithm_Implementationn

Topics: PE and COFF headers. #misc #book

Summary: 8 parts, 77 pages

This PDF contains information of PE/COFF headers and useful content if you want to extract informations from an executable.

Topics: Cryptography, C. #c #crypto #book

Summary: 5 parts, 30 pages.

This quick ebook shows you how to implement some cryptographic algorithms in C, such as AES, DES or SHA, you can find the structures of these algorithms in chapter 4.

Topics: Math. #math

Useful link about transcendental numbers, by the way, this site has a lot of resources for Algebra, Calculus and Applied Math in general.

https://mathworld.wolfram.com/TranscendentalNumber.html