GCC 14.0.0 Status Report (2023-11-20), Stage 3 in effect now

Status == The GCC development branch which will become GCC 14 is in general bugfixing mode (Stage 3) now. There is still time to get larger changes in that were posted before the end of Stage 1 but this is more aimed at fixing important bugs that are not regressions and maybe flesh out detail

GCC developer room at FOSDEM 2024: Call for Participation open

Hi! On 2023-11-10T18:20:55-0500, David Malcolm wrote: > We're excited to announce that GCC will have a developer room at the > upcoming FOSDEM 2024, in Brussels, Belgium: Now also announcing the devroom/CfP on , "News"; pushed commit 1825b255beb7d7edca775c401222ad2cb41ea193

Re: LRA for avr: Maintain live range info for pseudos assigned to FP?

Am 20.11.23 um 08:14 schrieb SenthilKumar.Selvaraj--- via Gcc: On Thu, 2023-10-05 at 15:33 -0400, Vladimir Makarov wrote: EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe On 9/7/23 07:21, senthilkumar.selva...@microchip.com wrote: Hi, One more

Reporitng libstdc++ bug without account to Bugzilla

Hi I think I found libstdc++ bug and I tried to report to Bugzilla but "user account creation has been restricted". So I'm going to report it here in hope that someone with a account could report it to Bugzilla if they seem it fit. Using gcc 13.2 with -std=c++23 code below (https://godbolt.org

Re: Reporitng libstdc++ bug without account to Bugzilla

On Mon, 20 Nov 2023 at 14:23, Palmu, Miro M wrote: > > Hi > > I think I found libstdc++ bug and I tried to report to Bugzilla but "user > account creation has been restricted". > > So I'm going to report it here in hope that someone with a account could > report it to Bugzilla if they seem it fit

Re: [PATCH 2/4] libbacktrace: detect executable path on windows

Hi, this is what I'm using with GCC 12 and 13 on my windows machines, rebased onto the current HEAD. Kind regards, Björn. Am 06.02.2023 um 01:22 schrieb Ian Lance Taylor: On Sun, Feb 5, 2023 at 1:21 AM Björn Schäpers wrote: Am 24.01.2023 um 19:32 schrieb Ian Lance Taylor: On Tue, Jan 24,

Re: [PATCH 3/4] libbacktrace: work with aslr on windows

An updated version, using neither A or W, but just the macro. Am 21.01.2023 um 12:42 schrieb Eli Zaretskii: Date: Sat, 21 Jan 2023 11:47:42 +0100 Cc: g...@hazardy.de, gcc-patc...@gcc.gnu.org, gcc@gcc.gnu.org From: Gabriel Ravier On 1/21/23 05:05, Eli Zaretskii wrote: Date: Fri, 20 Jan 2023 2

Re: [PATCH 3/4] libbacktrace: work with aslr on windows

> Date: Mon, 20 Nov 2023 20:57:38 +0100 > Cc: gcc-patc...@gcc.gnu.org, gcc@gcc.gnu.org > From: Björn Schäpers > > +#ifndef NOMINMAX > +#define NOMINMAX > +#endif Why is this part needed? Otherwise, LGTM, thanks. (But I'm don't have the approval rights, so please wait for Ian to chime in.)

function parameters

Hello #include void func(char *ptr) {     printf("\n%i",sizeof(ptr)); } int main(void) {     char arr[10];     printf("\n Sizeof arr %i",sizeof(arr));     func(arr);     return 0; } /* sizeof(arr) != sizeof(ptr), but they point to same thing. */ So problem. On main, arr has size 10, while

Re: function parameters

Am Dienstag, dem 21.11.2023 um 02:30 + schrieb André Albergaria Coelho via Gcc: > Hello > > #include > > void func(char *ptr) { >     printf("\n%i",sizeof(ptr)); > } > > int main(void) { >     char arr[10]; >     printf("\n Sizeof arr %i",sizeof(arr)); >     func(arr); > >     return

Question about creating an outermost loop

Hi, I'm working on loop tiling recently. I want to add this optimization to GCC. But I have encoutered some problems here and ask for help. For the code below as an example: for (int i = 0; i < 12; i++) { for (int j = 0; j < arr.length; j++) { // arr.length may be huge // do something with