Re: Fwd: Re: late generation of assemble code

2020-06-01 Thread Josh Stone
On 5/29/20 4:02 AM, Paul Dufresne via devel wrote: > * more space on the hard disks of the servers, because they contains > repositories only for LLVM IR packages rather than one by supported > architectures LLVM IR is not really arch-independent -- by the time you get to this level, all of the

Re: Fwd: Re: late generation of assemble code

2020-05-29 Thread John M. Harris Jr
On Friday, May 29, 2020 5:15:45 PM MST Colin Walters wrote: > On Fri, May 29, 2020, at 8:01 PM, John M. Harris Jr wrote: > > > > WebAssembly is just in web browsers. It's not for normal software you'd > > install with your package manager. Unless I'm missing something? > > > You are indeed

Re: Fwd: Re: late generation of assemble code

2020-05-29 Thread Colin Walters
On Fri, May 29, 2020, at 8:01 PM, John M. Harris Jr wrote: > WebAssembly is just in web browsers. It's not for normal software you'd > install with your package manager. Unless I'm missing something? You are indeed missing https://webassembly.org/docs/non-web/ https://wasi.dev/ More random

Re: Fwd: Re: late generation of assemble code

2020-05-29 Thread John M. Harris Jr
On Friday, May 29, 2020 1:56:16 PM MST Colin Walters wrote: > > Perhaps in Silverblue or other systems not designed to be a general > > purpose operating system? > > What, where did you get that? Silverblue is general purpose. Well, Silverblue is mostly GNOME. It's not meant for servers, etc.

Re: Fwd: Re: late generation of assemble code

2020-05-29 Thread Colin Walters
> Perhaps in Silverblue or other systems not designed to be a general purpose > operating system? What, where did you get that? Silverblue is general purpose. Anyways, my 2c on this topic: Once WebAssembly supports threads (it's coming) there's going to be a lot of interesting discussion

Re: Fwd: Re: late generation of assemble code

2020-05-29 Thread John M. Harris Jr
On Friday, May 29, 2020 4:02:40 AM MST Paul Dufresne via devel wrote: > had forgotten to reply also to the list... doing it now: > > [cut the part where it was suggested to make package that contains LLVM > Intermediate Representation bitcode rather than CPU specific assembler] > > > On

Fwd: Re: late generation of assemble code

2020-05-29 Thread Paul Dufresne via devel
had forgotten to reply also to the list... doing it now: [cut the part where it was suggested to make package that contains LLVM Intermediate Representation bitcode rather than CPU specific assembler] On 2020-05-29 1:01 a.m., John M. Harris Jr wrote: Paul, What benefit do you see in the

Re: late generation of assemble code

2020-05-28 Thread John M. Harris Jr
On Thursday, May 28, 2020 9:41:54 PM MST Paul Dufresne via devel wrote: > On 2020-05-28 7:36 a.m., Dridi Boukelmoune wrote: > > On Tue, May 26, 2020 at 12:07 PM Jan Kratochvil > > > > wrote: > >> On Sun, 24 May 2020 05:21:05 +0200, Paul Dufresne via devel wrote: > >>> The idea was to push code

Re: late generation of assemble code

2020-05-28 Thread Paul Dufresne via devel
On 2020-05-28 7:36 a.m., Dridi Boukelmoune wrote: On Tue, May 26, 2020 at 12:07 PM Jan Kratochvil wrote: On Sun, 24 May 2020 05:21:05 +0200, Paul Dufresne via devel wrote: The idea was to push code generation as near as possible of code execution. Because at execution time, you know what are

Re: late generation of assemble code

2020-05-28 Thread Dridi Boukelmoune
On Tue, May 26, 2020 at 12:07 PM Jan Kratochvil wrote: > > On Sun, 24 May 2020 05:21:05 +0200, Paul Dufresne via devel wrote: > > The idea was to push code generation as near as possible of code execution. > > Because at execution time, you know what are the specific features of the > > CPU, and

Re: late generation of assemble code

2020-05-26 Thread Jan Kratochvil
On Sun, 24 May 2020 05:21:05 +0200, Paul Dufresne via devel wrote: > The idea was to push code generation as near as possible of code execution. > Because at execution time, you know what are the specific features of the > CPU, and what is used to most often by the user of the program. In Free

Re: late generation of assemble code

2020-05-24 Thread Kevin Kofler
Paul Dufresne via devel wrote: > Is there some technical problems for not packaging LLVM code rather than > CPU specific code? First of all, we would have to use LLVM to begin with. The preferred compiler in Fedora is GCC, not Clang. There are other technical concerns, but this one is the most

Re: late generation of assemble code

2020-05-23 Thread Neal Gompa
On Sun, May 24, 2020 at 12:06 AM Paul Dufresne via devel wrote: > > On 5/23/20 11:26 PM, Neal Gompa wrote: > > On Sat, May 23, 2020 at 11:22 PM Paul Dufresne via devel > > wrote: > ... > > It's completely toast on Linux for the same reason FatELF was: nobody liked > > it. > > ... > > I think

Re: late generation of assemble code

2020-05-23 Thread Paul Dufresne via devel
On 5/23/20 11:26 PM, Neal Gompa wrote: > On Sat, May 23, 2020 at 11:22 PM Paul Dufresne via devel > wrote: ... > It's completely toast on Linux for the same reason FatELF was: nobody liked > it. ... I think this is different than FatELF. The idea of FatELF, is that it contains the generated

Re: late generation of assemble code

2020-05-23 Thread Neal Gompa
On Sat, May 23, 2020 at 11:22 PM Paul Dufresne via devel wrote: > > I sometime ask myself what have happened to the "LLVM dream"? > > The idea of LLVM was not to be *just* an intermediate language for the > compiler. The idea was to push code generation as near as possible of > code execution.

late generation of assemble code

2020-05-23 Thread Paul Dufresne via devel
I sometime ask myself what have happened to the "LLVM dream"? The idea of LLVM was not to be *just* an intermediate language for the compiler. The idea was to push code generation as near as possible of code execution. Because at execution time, you know what are the specific features of the