Office Hours for the GNU Toolchain on 2024-06-27 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2024-06-27 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Office Hours for the GNU Toolchain on 2024-05-30 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2024-05-30 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

gcc-wwwdocs branch master updated. 3e9f71f2c5ae175b2a4b209156f2241fa0646381

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 3e9f71f2c5ae175b2a4b209156f2241fa0646381 (commit) from

Invitation: Office Hours for the GNU Toolchain @ Thu May 30, 2024 11am - 12pm (EDT) (gcc@gcc.gnu.org)

Office Hours for the GNU Toolchain Thursday May 30, 2024 ⋅ 11am – 12pm Eastern Time - New York Location https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6

Invitation: Office Hours for the GNU Toolchain @ Monthly from 11am to 12pm on the last Thursday (EDT) (gcc@gcc.gnu.org)

Office Hours for the GNU Toolchain Monthly from 11am to 12pm on the last Thursday Eastern Time - New York Location https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6

Office Hours for the GNU Toolchain on 2024-04-25 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2024-04-25 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Office Hours for the GNU Toolchain on 2024-03-28 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2024-03-28 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Office Hours for the GNU Toolchain on 2024-02-29 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2024-02-29 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Re: New TLS usage in libgcc_s.so.1, compatibility impact

On 1/15/24 08:55, Adhemerval Zanella Netto wrote: > > > On 15/01/24 09:46, Szabolcs Nagy wrote: >> The 01/13/2024 13:49, Florian Weimer wrote: >>> This commit >>> >>> commit 8abddb187b33480d8827f44ec655f45734a1749d >>> Author: Andrew Burgess >>> Date: Sat Aug 5 14:31:06 2023 +0200 >>> >>>

Office Hours for the GNU Toolchain on 2024-01-25 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2024-01-25 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Office Hours for the GNU Toolchain on 2023-11-30 at 11am EST5EDT.

Office Hours for the GNU Toolchain on 2023-11-30 at 11am EST5EDT. Agenda: * https://gcc.gnu.org/wiki/OfficeHours#Next Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Re: Checks that autotools generated files were re-generated correctly

On 11/7/23 02:38, Maxim Kuvyrkov wrote: >> On Nov 6, 2023, at 21:19, Christophe Lyon >> wrote: >> >> Hi! >> >> On Mon, 6 Nov 2023 at 18:05, Martin Jambor >> wrote: >>> >>> Hello, >>> >>> I have inherited Martin Liška's buildbot script that checks that >>> all sorts of autotools generated

Office Hours for the GNU Toolchain on October 17th at 11am EDT.

Office Hours for the GNU Toolchain on October 17th at 11am EDT. Agenda: * First Office Hours and test of the meeting system. * No specific agenda will be presented, but feel free to attend. Meeting Link: * https://bbb.linuxfoundation.org/room/adm-xcb-for-sk6 -- Cheers, Carlos.

Re: [RFC] GCC Security policy

On 8/8/23 13:46, David Edelsohn wrote: > I believe that upstream projects for components that are imported > into GCC should be responsible for their security policy, including > libgo, gofrontend, libsanitizer (other than local patches), zlib, > libtool, libphobos, libcody, libffi, eventually

Re: git out-of-order commit (was Re: [PATCH] Fortran: Remove unused declaration)

On 1/19/23 23:26, Bernhard Reutner-Fischer wrote: > On 19 January 2023 20:39:08 CET, Jason Merrill wrote: >> On Sat, Nov 12, 2022 at 4:24 PM Harald Anlauf via Gcc-patches >> wrote: >>> >>> Am 12.11.22 um 22:05 schrieb Bernhard Reutner-Fischer via Gcc-patches: This function definition was

RFP is open for the Toolchains and Kernel Track at LPC 2022

The Linux Plumbers Conference 2022 (https://lpc.events) will be held from 12 to 14 of September 2022 in Dublin. As part of the conference we will be having a Toolchains and Kernel track that will focus on topics of interest related to building the Linux kernel, and kernel development in general.

Re: https://patchwork.sourceware.org/project/gcc/

On 9/29/21 07:22, Jonathan Wakely wrote: > On Wed, 29 Sept 2021 at 11:04, Thomas Schwinge > wrote: >> Also, we'll need some user guide: web page, or wiki page, or, >> preferably?, on itself. >> How are we using the different states, archived,

The official glibc IRC channel is now on OFTC as #glibc.

Community, The official glibc IRC channel is now on OFTC as #glibc. gcc developers, please feel free to visit #glibc :-) We also have an unofficial IRC channel #glibc on Libera.Chat -- Cheers, Carlos.

Re: New x86-64 micro-architecture levels

On 7/22/20 6:34 AM, Florian Weimer wrote: > * Jan Beulich: > >> On 21.07.2020 20:04, Florian Weimer wrote: >>> * Premachandra Mallappa: >>> [AMD Public Use] Hi Floarian, > I'm including a proposal for the levels below. I use single > letters for them, but I expect

Re: New x86-64 micro-architecture levels

On 7/22/20 5:26 AM, Richard Biener via Libc-alpha wrote: > So for the bike-shedding I indeed think x86-10{0,1,2,3} > or x86-{A,B,C,..}, eventually duplicating as x86_64- as > suggested by Jan is better than x86-2014 or x86-avx2. Agreed. If we really want to be clear, call it a "level" or

Re: Separate commit mailing lists for trunk/branches possible?

On 7/17/20 3:41 PM, Florian Weimer wrote: > * Carlos O'Donell via Gcc: > >> FYI, for glibc we use the AdaCore git commit hooks (like gdb). >> >> There we use this configuration: >> >> # Only send emails for master and release branches. >>

Re: Separate commit mailing lists for trunk/branches possible?

On 7/17/20 2:11 PM, Frank Ch. Eigler via Overseers wrote: > Hi - > >> Would it be reasonable to have the mailing list split into more than >> one, that is at least the original covering the trunk, and then one >> or more for branches? [...] > > (This matter is for the gcc community to decide.