<Entei[m]>
Just checking out the gcc rebuild the next day, I seriously doubt allocating 20 cores increased the performance....Any way to heck measure the impact? It seems to be using not more than 2-4 cores at a time, all other cores are almost idle most of the time
<Entei[m]>
s/heck//
<Entei[m]>
I was expecting a package like gcc would saturate all cores to max utilisation, instead I see qemu having not more than 200% cpu load
<Entei[m]>
Oh very quick update. All 20 cores just lit up.
<davidlt[m]>
It's probably configure stuff, which is basically a single thread.
<davidlt[m]>
During those times, QEMU is slow compared to the boards.
<Entei[m]>
davidlt[m]: Yeah it's snail pace. Would really like to see better boards(with more cores) soon for building purposes and setting up Koji.
<davidlt[m]>
64 core should be available soon.
<davidlt[m]>
TBD if that is actually faster.
<davidlt[m]>
Oh, there will be a new GCC 13 build in the F38.
<Entei[m]>
What's the xgcc thing in the build process? My senior said gcc compiles in 3 stages. But I made sure all bootstrapping was disabled...
<davidlt[m]>
That's a gcc already built IIRC.
<Entei[m]>
davidlt[m]: So `xgcc` is my system's preinstalled gcc?
<davidlt[m]>
No, it's built part of the build process IIRC.
<dtometzki>
Hello what i see xgccc will build in the first stage
<davidlt[m]>
> @itemize @bullet
<davidlt[m]>
> @item @code{./xgcc -B.}
<davidlt[m]>
> is the usual way to invoke a self-built GCC from within the @file{BUILDDIR/gcc}
<davidlt[m]>
> subdirectory.
<Entei[m]>
So the preinstalled gcc builds `xgcc`, which in turn builds the proper gcc (with specified language support). Is that correct?
<Entei[m]>
How exactly is this different from bootstrapping then?
<davidlt[m]>
I am not a GCC developer, but IIRC xgcc is a symlink to allow using GCC built it the last stage.
<davidlt[m]>
So you have 1 stage, you build a GCC, you use it (xgcc) and build all the libraries, etc.
<davidlt[m]>
At the install time it will be installed as gcc in the final location.
<davidlt[m]>
it's just that during the build process you need to refer to the last built GCC. You cannot use system GCC to build, e.g. standard C++ library.
<Entei[m]>
<davidlt[m]> "it's just that during the..." <- Ahh! That makes sense, then it would be no different otherwise. I am building for `rv64g`, and simply building the libraries with system compiler would result in libraries with `rv6gc`.
<Entei[m]>
In other cases this would result in complete ABI changes for libraries.
jednorozec has quit [Server closed connection]
jednorozec has joined #fedora-riscv
jcajka has joined #fedora-riscv
<davidlt[m]>
A new stable 6.3 kernel landed. Incl. a couple of RISCV patches.
<davidlt[m]>
<sajcho> "I'm sorry to bother you. Is..." <- Let me try to check.
<davidlt[m]>
It seems okay, but without testing it would be hard to be 100% sure.
droidrage has quit [Ping timeout: 246 seconds]
<sajcho>
Thank you.
sajcho has quit [Quit: Client closed]
masami has quit [Quit: Leaving]
zsun has joined #fedora-riscv
<davidlt[m]>
MilkV Pioneer is at V1.1 right now IIUC.
<thefossguy>
I assume if that's a standard extension, toolchain support isn't the headache/responsibility of the hardware vendor (for the very initial stages).
<davidlt[m]>
M?
<thefossguy>
what's that?
<davidlt[m]>
Didn't understand the "standard extension" part. Maybe I missed something.
<thefossguy>
I mean an extension that is ratified by the RISC-V foundation
<davidlt[m]>
Which one?
<thefossguy>
Not a vendor (read: proprietary) extension nor an extension that hasn't been ratified
<thefossguy>
I meant to ask that for RVV 1.1 :D
<davidlt[m]>
No, it's Version 1.1 :)
<davidlt[m]>
Not vector stuff :)
<thefossguy>
So, since it's an "open standard extension", I assume the vendor doesn't need to send patches upstream before the hardware reaches the hands of their customers but the stuff still works?
<thefossguy>
davidlt[m]: Oh, my bad XD
<davidlt[m]>
Well it's IP/SoC/CPU vendors that work on open source implementation.
<davidlt[m]>
RVI doesn't do that.
<thefossguy>
Ah, gotcha
<thefossguy>
Well not exactly a gotcha but now I know which rabbit hole to go down into :D