GNU cargo

2025-07-14 Thread The Cuthour via Gcc
I think Rust's cargo is a de facto standard build system and package manager, tightly integrated with the language and compiler. I'm proposing something similar for C and C++: - cargo-c for C - cargo-cc for C++ - cargo-s for assembler Each one would support: - Detecting all modified fi

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread Richard Biener via Gcc
On Tue, Jul 15, 2025 at 3:26 AM H.J. Lu via Gcc wrote: > > On Tue, Jul 15, 2025 at 8:47 AM 'Florian Weimer' via X86-64 System V > Application Binary Interface wrote: > > > > * H. J. Lu: > > > > > Compilers will never know since the build-time glibc is independent of > > > the run-time glibc. If

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread Florian Weimer via Gcc
* H. J. Lu: > On Tue, Jul 15, 2025 at 8:47 AM 'Florian Weimer' via X86-64 System V > Application Binary Interface wrote: >> >> * H. J. Lu: >> >> > Compilers will never know since the build-time glibc is independent of >> > the run-time glibc. If compilers want to be 100% sure that the run-time

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread Sam James via Gcc
Florian Weimer writes: > * H. J. Lu: > >> Compilers will never know since the build-time glibc is independent of >> the run-time glibc. If compilers want to be 100% sure that the run-time >> is GNU2 TLS bug-free, they can require linkers which generate the >> GLIBC_ABI_GNU2_TLS dependency. > >

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread H.J. Lu via Gcc
On Tue, Jul 15, 2025 at 8:47 AM 'Florian Weimer' via X86-64 System V Application Binary Interface wrote: > > * H. J. Lu: > > > Compilers will never know since the build-time glibc is independent of > > the run-time glibc. If compilers want to be 100% sure that the run-time > > is GNU2 TLS bug-fr

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread Florian Weimer via Gcc
* H. J. Lu: > Compilers will never know since the build-time glibc is independent of > the run-time glibc. If compilers want to be 100% sure that the run-time > is GNU2 TLS bug-free, they can require linkers which generate the > GLIBC_ABI_GNU2_TLS dependency. (Such a linker requirement could be

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread H.J. Lu via Gcc
On Tue, Jul 15, 2025 at 7:55 AM Florian Weimer wrote: > > * Adhemerval Zanella Netto: > > >> (b) Introduce binary markup to indicate that binaries may need the glibc > >> fix, and that glibc has the fix. > >> > >> [PATCH] x86-64: Add GLIBC_ABI_GNU2_TLS [BZ #33129] > >> > >>

Re: Switching x86-64 to GNU2 TLS descriptors

2025-07-14 Thread Florian Weimer via Gcc
* Adhemerval Zanella Netto: >> (b) Introduce binary markup to indicate that binaries may need the glibc >> fix, and that glibc has the fix. >> >> [PATCH] x86-64: Add GLIBC_ABI_GNU2_TLS [BZ #33129] >> >> >>

Re: Help with RTL/MD needed

2025-07-14 Thread Jeff Law via Gcc
On 7/14/25 10:57 AM, Jan Dubiec via Gcc wrote: Recently I have started playing with machine descriptions in the context of PR109324 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109324). I have nodified MDs (see the attached patch) and got following ICE when I tried to build gcc: /d/Works/

Re: Pushing a lot of commits to an old branch

2025-07-14 Thread Andi Kleen via Gcc
Thomas Koenig via Gcc writes: > Hi, > > there is a branch I want to update. Git currently tells me > > Your branch is ahead of 'origin/devel/coarray_native' by 28906 commits. > There are still a few ChangeLog entries to clean up, I'll make sure > that contrib/gcc-changelog/git_check_commit.py pas

Help with RTL/MD needed

2025-07-14 Thread Jan Dubiec via Gcc
Recently I have started playing with machine descriptions in the context of PR109324 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109324). I have nodified MDs (see the attached patch) and got following ICE when I tried to build gcc: /d/Works/xcomp/gcc-build-stage1/./gcc/xgcc -B/d/Works/xcomp

Re: Addition of compiler flag for dynamic_cast optimization

2025-07-14 Thread Thomas de Bock via Gcc
I had not, but here is some code which I compiled with the same gcc version, the only difference being that in one, I had the optimization enabled: #include #include #include struct A { virtual ~A() {} }; struct B final : A { virtual ~B() {} }; B* __attribute__ ((noinline)) dc(A* a) {

Re: Addition of compiler flag for dynamic_cast optimization

2025-07-14 Thread Jonathan Wakely via Gcc
On Mon, 14 Jul 2025 at 14:57, Thomas de Bock via Gcc wrote: > > Hello all, I've been looking into a compiler optimization implemented by > clang but not gcc that substitutes a __dynamic_cast call for a simple vtable > ptr comparison in the case that the class being cast to is final. > > However

Addition of compiler flag for dynamic_cast optimization

2025-07-14 Thread Thomas de Bock via Gcc
Hello all, I've been looking into a compiler optimization implemented by clang but not gcc that substitutes a __dynamic_cast call for a simple vtable ptr comparison in the case that the class being cast to is final. However this brings issues with it in some cases (specified in thread). I belie

Re: GCC 12.5 Released

2025-07-14 Thread Jakub Jelinek via Gcc
On Mon, Jul 14, 2025 at 10:19:43AM +0100, Richard Earnshaw (lists) via Gcc wrote: > On 14/07/2025 08:04, Richard Biener via Gcc wrote: > > On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc > > wrote: > >> > >> Hello Richard, > >> > >> Thank you for making these announcements, they are very u

Re: GCC 12.5 Released

2025-07-14 Thread Richard Earnshaw (lists) via Gcc
On 14/07/2025 08:04, Richard Biener via Gcc wrote: > On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc wrote: >> >> Hello Richard, >> >> Thank you for making these announcements, they are very useful and >> informative. But I have one small request to make. Please include a link to >> the web

Re: GCC 12.5 Released

2025-07-14 Thread Richard Biener via Gcc
On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc wrote: > > Hello Richard, > > Thank you for making these announcements, they are very useful and > informative. But I have one small request to make. Please include a link to > the web page that describes the changes from the last release. The