Re: ELF2.0: Linkable struct

2025-01-31 Thread The Cuthour via Gcc
Hi C++ requires constant expressions to be known during compilation, not at link time. A constant that is not determined at compile-time is akin to constructor that is const but not constexpr. While it remains constant throughout the program, its value is established only at link-time, not a

Re: ELF2.0: Linkable struct

2025-01-31 Thread The Cuthour via Gcc
Hi On 2025/01/31 18:47, Jonathan Wakely wrote: On Fri, 31 Jan 2025 at 08:28, The Cuthour wrote: On 2025/01/31 17:05, Jonathan Wakely wrote: On Fri, 31 Jan 2025, 06:50 The Cuthour via Gcc, mailto:gcc@gcc.gnu.org>> wrote: Suppose we have the following two classes: ===

Re: ELF2.0: Linkable struct

2025-01-31 Thread The Cuthour via Gcc
On 2025/01/31 17:05, Jonathan Wakely wrote: On Fri, 31 Jan 2025, 06:50 The Cuthour via Gcc, <mailto:gcc@gcc.gnu.org>> wrote: Suppose we have the following two classes: === Vec.h === class Vec {      int x, y, z; }; === end Vec.h === === Pix.h ===

Re: ELF2.0: Linkable struct

2025-01-30 Thread The Cuthour via Gcc
Hi struct image { vec2 pos[2]; std::vector pixels; }; Now if any of those structs are modified, members added or removed, it would require recompilation of the whole code that uses it. This is because the memory offsets to access the fields change and might fall out of the displacement r

ELF2.0: Linkable struct

2025-01-30 Thread The Cuthour via Gcc
Suppose we have the following two classes: === Vec.h === class Vec { int x, y, z; }; === end Vec.h === === Pix.h === class Pix: Vec { int r, g, b; }; === end Pix.h === If we add or remove a member variable in class Vec, it requires recompiling not only Vec.cc but also Pix.cc. I believ

Re: Link-time resolved constant

2025-01-08 Thread The Cuthour via Gcc
And I heard "That's already here. ELF gABI does the same thing." Anyway I can't implement it myself. I hope wide discussion. https://gcc.gnu.org/pipermail/gcc/2025-January/245358.html On 2025/01/08 22:08, Trampas Stern wrote: Go do it! Do it so well and with such high quality that no one can

RFC: Link-time resolved constant

2025-01-07 Thread The Cuthour via Gcc
Previous thread on binutils https://sourceware.org/pipermail/binutils/2025-January/138334.html I'd like to hear your opinion. Can we once again promise that only modified files need to be recompiled?

Re: Link-time resolved constant

2025-01-07 Thread The Cuthour via Gcc
Thank you. My plan is to make a higher compatibility version of ELF. You may be able to call it ELF2.0

Link-time resolved constant

2025-01-07 Thread The Cuthour via Gcc
Previous thread on binutils https://sourceware.org/pipermail/binutils/2025-January/138334.html I'd like to hear your opinion. Can we once again promise that only modified files need to be recompiled?