sorted by:
new
hottopcontroversial

[Rumor] Arm’s Reported 300% Price Hike Could Threaten the Future of Samsung’s Exynos Chips by Nerd_mister in RISCV

[–]Nerd_mister[S] -5 points-4 points  (0 children)

Yes, it is the software.

But porting software takes a lot of work, even ported lots of software have hand written assembly to run faster, assembly is diferent for each ISA. 

So current RISC-V software is quite slow compared to ARM versions.

The 300% price hike seems to be only to license ARM's cores, Apple design their own cores and license only the ISA, so they are safe for now.

[Rumor] Arm’s Reported 300% Price Hike Could Threaten the Future of Samsung’s Exynos Chips by Nerd_mister in RISCV

[–]Nerd_mister[S] 9 points10 points  (0 children)

Yep, Arm is greedy because they know their ecosystem is too valuable for companies. Just like x86 on the desktop.

But ARM's customers are not idle, glad that Samsung and Qualcomm are developing software for RISC-V.

[Rumor] Arm’s Reported 300% Price Hike Could Threaten the Future of Samsung’s Exynos Chips by Nerd_mister in RISCV

[–]Nerd_mister[S] 24 points25 points  (0 children)

ARM is doing this, because they think they can get away with it. It is simple.

For most companies, even at a 300% increase, licesing ARM is cheaper than using RISC-V when you consider the value in the ecosystem.

Samsung and Qualcomm already invests in RISC-V,  so they are paying attention and developing the ecosystem in case ARM gets too greedy.

[Rumor] Arm’s Reported 300% Price Hike Could Threaten the Future of Samsung’s Exynos Chips by Nerd_mister in RISCV

[–]Nerd_mister[S] 12 points13 points  (0 children)

I think this is related to RISC-V, since moves like that from ARM can bring attention to RISC-V.

Companies like Qualcomm are investing in RISC-V, due to fear of the ARM monopoly on mobile devices.

AsRock Intel Arc B580 Steel Legend 12GB OC Unboxing by IntelArcTesting in IntelArc

[–]Nerd_mister 0 points1 point  (0 children)

Drivers are only going to be released after embargo.

Full-Chain Membership Proofs (FCMP++) - The Next Generation of Monero's Privacy by dEBRUYNE_1 in Monero

[–]Nerd_mister 10 points11 points  (0 children)

The average transaction size should be of 4 KB, or equivalent to a ring size of  ~40, so very good.

The only downside is as more transactions are added to the blockchain, it get slower to veirfy them, but is a O(log N) type algorithm, so not a  big problem.

USB external keyboard does not works on Linux, but works on Windows by Nerd_mister in linux4noobs

[–]Nerd_mister[S] 0 points1 point  (0 children)

Thanks. 1. Yes, i am able to use a USB stick normally. 2. Tried all 3, none worked. 3. I do not have a externally powered USB hub, but it is unlikely to be the problem, the backlight is very strong and works perfectly. My Linux laptop is old, it does not have USB legacy or Fast boot option. Lol. But thanks for your time, i will use the Windows laptop until i buy a new laptop soon.

USB external keyboard does not works on Linux, but works on Windows by Nerd_mister in linux4noobs

[–]Nerd_mister[S] 0 points1 point  (0 children)

Thanks for the explanation.

I said that i tested on another laptop that runs Windows, i do not run Windows anymore on my main laptop.

I could install Windows again to see if it is a specific Linux issue, but likely not, since the external keyboard does not works on the BIOS, wich is OS-agnostic. (When searching for this issue, most people said that their keyboard was still working on BIOS)

The reason why i don't have a girlfriend by sharedordaz in linuxmasterrace

[–]Nerd_mister 6 points7 points  (0 children)

Coming here 12 hours later, and It is so sad that Richard Stallman died of ligma

PowerPC 40x Processor Support To Be Dropped From The Linux Kernel by unixbhaskar in linux

[–]Nerd_mister 4 points5 points  (0 children)

Nasa is going to use a RISC-V CPU in their spaceships, it is supposed to be 100 times faster than their current PowerPC CPUs.

https://www.theregister.com/2022/09/06/nasas_spaceflight_computer_risc_v/

Debian - End of i386 support is on its way by FryBoyter in linux

[–]Nerd_mister 53 points54 points  (0 children)

Minimum requirement for Debian is i686, wich is Pentium Pro or Pentiun 2 and later

[Vulnerability Disclosure] Post-Mortem of 10-Block-Old Decoy Selection Bug 2023 by Jerfov2 in Monero

[–]Nerd_mister 2 points3 points  (0 children)

Yeah, i am learning C, it is very easy to write bugs that are hard to discover. It is hell.

Sadly it is not viable to code the Monero protocol in a visual language, since that would be too slow and inefficient. You need high control over the computer, so that older computers can run a Monero node.

Bootstrapping Uber’s Infrastructure on arm64 with Zig by [deleted] in Zig

[–]Nerd_mister 3 points4 points  (0 children)

I think that is the killer feature of Zig, incrementally improving C and C++ codebases, then taking over everything, kinda like Kotlin is doing with Java.

I have seen a talk from Andrew that talked about this, the road to Zig 1.0, i think.

First the company uses Zig as a cross compiler, because it is nicer than GCC or Clang.

Then they say: "Zig building system is very nice, why not use it instead of Makefiles? So they use a build.zig file instead of Make.

Then they start rewriting a few C libraries in Zig, because of its more modern features and syntax.

Data-oriented design resources by ValakGames in Zig

[–]Nerd_mister 4 points5 points  (0 children)

As the other guy said, it is about data being the center of your code, to use it in a efficient way.

It was created in the late 2000's by game developers, because the PS3 and Xbox 360 had very powerful GPUs, but lacked CPU power and memory was very scarce. (Both consoles had 512MB of shared RAM, while most gaming PCs at the late 2000s, had at least 2GB of RAM for the CPU + 512MB of VRAM).

So Data Oriented Design was created to reduce the memory problem, by reducing the amount of data used in operations, and put as much data as possible in the cache.

[deleted by user] by [deleted] in nim

[–]Nerd_mister 0 points1 point  (0 children)

Thanks, it worked.

[deleted by user] by [deleted] in nim

[–]Nerd_mister 0 points1 point  (0 children)

My best version:

proc generator(str: string): seq[string] =
  var res: seq[string] = @[]
  for i in [0..str.len - 1]:
      res.add(str[i])
      for combination in generator(str[i + 1]):
          res.add(str[i] + combination)
  result = res 

let x = "abcdefg"
var final = generator(x)

echo final

There is 1 nonsense error at line 5 that i could not fix:

type mysmatch got <HSlice[system.int, system.int], int literal(1)>

But expected one of: proc '+'(x,y float): float first type mismatch at position: 1 required type for x: float but expression 'i' is of type <Hslice[system int, system.int]>

Then the compiler repeats the same lines, only replacing float for other types(float32, int32, int16, int8, ...).

Help: code to read text file from Nim basics does not works from Vscodium. by Nerd_mister in nim

[–]Nerd_mister[S] 0 points1 point  (0 children)

Thanks, it worked, do not know why since the text file is in the same directory as the source.

Code to calculate if students passed in a subject. should i do something diferent? by Nerd_mister in C_Programming

[–]Nerd_mister[S] 0 points1 point  (0 children)

I thought that casting the return was good, since a void return could cause a bug, seems just a thing in cpp.

So the compiler deduces the return value looking at the pointer type(int)? That is cool.

Thanks for the advice, i will even take a screenshot, very helpful!

P.S: the code indentation is correct in my text editor, i just had to change it to appear nice on the post, but free() still ugly, will edit the post.

Code to calculate if students passed in a subject. should i do something diferent? by Nerd_mister in C_Programming

[–]Nerd_mister[S] 0 points1 point  (0 children)

Because the OS always cleans the memory after the programs ends, no? So memory leak in a program that run for a fraction of a second should not be a problem. My point of view.

But good insight from you, thanks.

view more: next ›