Re: "file name" vs "filename"

2023-04-17 Thread James K. Lowden
On Sat, 15 Apr 2023 00:00:44 +0200 (CEST) Gerald Pfeifer wrote: > On Mon, 2 Apr 2018, Joseph Myers wrote: > > See the GNU Coding Standards: > > > > Please do not use the term ``pathname'' that is used in Unix > > documentation; use ``file name'' (two words) instead. We use the > > term ``pa

Re: GCC-13 Branch with RISC-V Performance-Related Backports

2023-04-17 Thread Jeff Law via Gcc
On 4/17/23 12:50, Palmer Dabbelt wrote: Based on some discussions, it looks like a handful of vendors are planning on maintaining GCC-13 branches that include various performance-related backports (ie, patches not suitable for the standard GCC-13 release branch). I don't think we'd actuall

GCC-13 Branch with RISC-V Performance-Related Backports

2023-04-17 Thread Palmer Dabbelt
Based on some discussions, it looks like a handful of vendors are planning on maintaining GCC-13 branches that include various performance-related backports (ie, patches not suitable for the standard GCC-13 release branch). I don't think we'd actually agreed to a set of branch rules, but it s

RISC-V GCC Patchwork Sync-Up Meeting

2023-04-17 Thread Palmer Dabbelt
The topic of having some sort of RISC-V development meeting has come up a handful of times, but we never got around to actually setting anything up. We've had a patchwork sync meeting for the RISC-V Linux port for a few months now and it's been super helpful, I figured it be best to just do so

GCC 14.0.0 Status Report (2023-04-17)

2023-04-17 Thread Jakub Jelinek via Gcc
Status == The trunk has branched for the GCC 13 release and is now open again for general development, stage 1. Please consider not disrupting it too much during the RC phase of GCC 13 so it is possible to test important fixes for 13.1 on it. Quality Data Priority #

GCC 13.0.1 Status Report (2023-04-17)

2023-04-17 Thread Jakub Jelinek via Gcc
Status == We have reached zero P1 regressions today and releases/gcc-13 branch has been created. GCC 13.1-rc1 will be built likely tomorrow. The branch is now frozen for blocking regressions and documentation fixes only, all changes to the branch require a RM approval now. If no show stopper

RE: Axway users

2023-04-17 Thread Annie Nicholson via Gcc
Hi there, Did you review the email below? Let me know your thoughts! Best regards, Annie From: Annie Nicholson Sent: Wednesday, April 5, 2023 8:58 AM To: 'gcc@gcc.gnu.org' Subject: Axway users Hi there, Greetings! Trust this mail finds you well! Would you be interested in the following users

GCC 12.2.1 Status Report (2023-04-17)

2023-04-17 Thread Richard Biener via Gcc
Status == The gcc-12 branch is open for regression and documentation fixes. It's time to do the annual release from the branch, GCC 12.3, and the planning is to do a release candidate at the start of the first week of May following with the actual release in the second week. Please look thro

RISC-V V C Intrinsic API v1.0 release meeting reminder (April 17th, 2023)

2023-04-17 Thread Eop Chen via Gcc
Hi all, A reminder that the next open meeting to discuss on the RISC-V V C Intrinsic API v1.0 is going to be held later on 2023/04/17 6AM (GMT -7) / 11PM (GMT +8). The agenda can be found in the second page of the meeting slides (link