From: Mark Wielaard <mark@klomp.org>
To: gcc@gcc.gnu.org, binutils@sourceware.org, newlib@sourceware.org,
libc-alpha@sourceware.org, gdb@sourceware.org,
systemtap@sourceware.org, libabigail@sourceware.org,
valgrind-developers@lists.sourceforge.net
Subject: Core Toolchain and Developer Tools at FOSDEM
Date: Sun, 28 Jan 2024 21:38:42 +0100 [thread overview]
Message-ID: <20240128203842.GE15739@gnu.wildebeest.org> (raw)
Fosdem is next weekend, February 3 & 4, in Brussels. Guinevere,
Dodji, Jose, David and Thomas organized some great devroom talks:
On Saturday, 15:00 to 18:20, the Debugger and Analysis Devroom
https://fosdem.org/2024/schedule/track/debuggers-and-analysis/
Debug your stage-1 systemd with GDB and the NixOS test framework
Ryan Lahfa, Julien Malka, Linus Heckemann
Love rr, Love rr, you're so good to me
Vicențiu Ciorbaru
Help us improve time manipulation with GDB
Guinevere Larsen
ROCgdb, GDB and AMDGPU debugging
Lancelot SIX
GDB on Windows: status & plans
Pedro Alves
Online Debugging and ABI Data Services
Frank Ch. Eigler
Poke all the microcontrollers!
Mohammad-Reza Nabipoor
Verrou : a valgrind tool dedicated to floating point error diagnosis
LATHUILIERE Bruno
Also on Saturday from 11:40 to 12:20 in the Rust devroom Arthur Cohen
will talk about The plan for gccrs
https://fosdem.org/2024/schedule/event/fosdem-2024-2207-the-plan-for-gccrs/
On Sunday, from 9:00 to 12:45, the GCC devroom
https://fosdem.org/2024/schedule/track/gcc/
Welcome to the GCC dev room
David Malcolm, Thomas Schwinge
GCC for new contributors
David Malcolm
How to bring up GCC for your new chip
Jeremy Bennett
My experience as a first time contributor to GCC's LTO
Rishi Raj
Unicode Support for GCC Rust
Raiki Tamura
What can Compiler-Explorer do for GCC
Marc Poulhiès
Unlocking Secret Analysis in GCC Static Analyzer
Pierrick Philippe
Yacking about Bison
James Lowden
Can the mold linker be /usr/bin/ld?
Rui Ueyama
Build Distribution for Maintaining the Famous GCC 4.7
Oliver Reiche
Sega Dreamcast Homebrew with GCC
Falco Girgis
Various Sourceware volunteers, overseers, PLC members and Software
Freedom Conservancy staff will also be around.
For those we cannot attend in person the talks will be recorded.
reply other threads:[~2024-01-28 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240128203842.GE15739@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libabigail@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=newlib@sourceware.org \
--cc=systemtap@sourceware.org \
--cc=valgrind-developers@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).