Re: The GNU Toolchain Infrastructure Project

2022-10-07 Thread Mark Wielaard
Hi, On Thu, 2022-10-06 at 17:37 -0400, Siddhesh Poyarekar wrote: > Also as I responded to Mark, the technical details of the transition are > the responsibility of the GTI TAC (which you were invited to be member > of and you declined) and not the LF IT, although they'd be the ones > implementi

Re: The GNU Toolchain Infrastructure Project

2022-10-12 Thread Mark Wielaard
Hi David, On Tue, Oct 11, 2022 at 01:14:50PM -0400, David Edelsohn wrote: > an alternative proposal? When were they allowed to participate in the > preparation of the "Sourceware" proposal, supposedly for their benefit? It wasn't really meant as an alternative proposal. And tt shouldn't be in con

Re: The GNU Toolchain Infrastructure Project

2022-10-12 Thread Mark Wielaard
Hi Florian, On Wed, Oct 12, 2022 at 03:18:55PM +0200, Florian Weimer wrote: > * Mark Wielaard via Overseers: > > And it is a about having a public discussion. > > > > - Sourceware roadmap discussions > > https://sourceware.org/pipermail/overseers/2022q2/018453.html &

Re: Toolchain Infrastructure project statement of support

2022-10-17 Thread Mark Wielaard
Hi Carlos, On Wed, Oct 12, 2022 at 12:43:09PM -0400, Carlos O'Donell wrote: > The GNU Toolchain project leadership [...] I must say I don't understand why you are communicating in this way. Sending out "proclamations" about having support from "leadership", "committees" and "key stakeholders". So

Re: Toolchain Infrastructure project statement of support

2022-10-18 Thread Mark Wielaard
Hi Siddhesh, On Mon, Oct 17, 2022 at 12:11:53PM -0400, Siddhesh Poyarekar wrote: > There seems to be little to discuss from the GNU toolchain perspective IMO; Yes, it is clear you don't want any discussion or answer any questions about the proposals, how funds can be used, what the budget is, wha

DWZ 0.15 released

2022-11-03 Thread Mark Wielaard
shortlog = Lv Ying (1): Fix handling readelf following links by default Mark Wielaard (11): Mark and init shstrtab[_len] and const in optimize_multifile Workaround binutils readelf following and printing alt file. Print abbrev or DIE offset for Unknown DWARF error message. Remove double

Re: Announcement: Porting the Docs to Sphinx - tomorrow

2022-11-09 Thread Mark Wielaard
Hi, On Wed, Nov 09, 2022 at 08:49:22AM +0100, Richard Biener via Gcc wrote: > On Wed, Nov 9, 2022 at 1:09 AM Sam James via Gcc-patches > wrote: > > > On 9 Nov 2022, at 00:00, Joseph Myers wrote: > > > On Tue, 8 Nov 2022, Sam James via Gcc wrote: > > > > If that's your expectation, that's fine, b

Re: gcc.gnu.org/wiki/ – broken because /moin_static1910/ files fail with 404

2022-11-11 Thread Mark Wielaard
Hi Tobias, On Fri, Nov 11, 2022 at 09:14:17AM +0100, Tobias Burnus wrote: > this seems to be a very recent regression: https://gcc.gnu.org/wiki/ > is currently only limited usable. > > Looking at the browser console, the problem is: > > GET https://gcc.gnu.org/moin_static1910/common/js/common.js

gcc@gcc.gnu.org

2022-11-15 Thread Mark Wielaard
This Friday, 18 November, at 16:00 UTC (11:00am Eastern, 17:00 Central European Time) the FSF will host a session on their BBB server about the current sourceware infrastructure and future plans. https://www.fsf.org/events/sourceware-infrastructure-a-presentation-and-community-q-a https://inbox.so

Re: testsuite under wine

2022-12-24 Thread Mark Wielaard
Hi, On Fri, Dec 23, 2022 at 10:00:36PM -0600, Jacob Bachmeyer via Gcc wrote: > NightStrike wrote: > > Rust is getting \r\r\n\n (as opposed to \r\n\r\n), so... yeah. Could > > be the rust test, could be the rust frontend, could be another weird > > Wine interaction. > > That is probably either a

gcc@gcc.gnu.org

2022-12-31 Thread Mark Wielaard
On Tue, Nov 15, 2022 at 10:45:32PM +0100, Mark Wielaard wrote: > https://www.fsf.org/events/sourceware-infrastructure-a-presentation-and-community-q-a > https://inbox.sourceware.org/overseers/6e9cde97-d880-5343-6cfd-16a648cf6...@fsf.org/ > > We like to discuss how to use the new in

Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-30 Thread Mark Wielaard
Hi Steve, On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote: > Please remove the skull and cross bones in the subject line. That is the default "hazard symbol" buildbot uses if a build turns from success to failure. If you have a better suggestion you might want to contact upstream htt

Sourceware network outage, Tuesday 2023-01-31

2023-01-30 Thread Mark Wielaard
We've received word from our data centre hosts that they will have a network infrastructure outage tomorrow, Tuesday 2023-01-31, between 8am and 12am EST (UTC-5). We may follow that up with a server firmware-related update/boot. This impacts sourceware.org, builder.sourceware.org, patchwork.source

Re: Stepping down as gcov maintainer and callgraph reviewer

2023-02-16 Thread Mark Wielaard
Hi Martin, On Thu, 2023-02-16 at 16:54 +0100, Martin Liška wrote: > After spending last decade (including my diploma thesis even more) > of my life working on GCC, I decided to leave the project and try > a different job. I would like to thank all the community members I had > change to interact w

Re: Missed warning (-Wuse-after-free)

2023-02-17 Thread Mark Wielaard
On Fri, 2023-02-17 at 08:38 -0500, Siddhesh Poyarekar wrote: > On 2023-02-17 06:22, Alejandro Colomar wrote: > > Hi Siddhesh, > > > > On 2/17/23 04:48, Siddhesh Poyarekar wrote: > > > On 2023-02-16 10:15, David Malcolm via Gcc wrote: > > > > I'm not convinced that it's useful to the end-user to wa

Sourceware infrastructure updates Q1 2023

2023-03-08 Thread Mark Wielaard
and organisations for maintaining and/or providing hardware for builder.sourceware.org Brno University, Dan Horák, Marist University, Thomas Fitzsimmons, Mark Wielaard, Frank Eigler, IBM, Carl Love, The Works on Arm initiative, Christophe Lyon, and Red Hat

Re: [GSoC] gccrs Unicode support

2023-03-16 Thread Mark Wielaard
Hi, On Thu, 2023-03-16 at 10:28 +0100, Thomas Schwinge wrote: > I'm now also putting Mark Wielaard in CC; he once also started discussing > this topic, "thinking of importing a couple of gnulib modules to help > with UTF-8 processing [unless] other gcc frontends handle [these t

Re: Website https://gcc.gnu.org/ down

2023-03-25 Thread Mark Wielaard
Hi Damian, On Sat, Mar 25, 2023 at 07:30:14AM +0100, Damian Tometzki wrote: > the website and git https://gcc.gnu.org/ is down ? > > Any info about it ? The site isn't down, but there is an issue (ddos?) with the fsf dns servers for gnu.org. The FSF tech team announces downtime and temporary iss

Re: Hosting our gfortran MatterMost workspace

2023-04-28 Thread Mark Wielaard
Hi Jerry, Hi Andrew, On Fri, Apr 28, 2023 at 09:16:12AM -0700, Andrew Pinski via Gcc wrote: > On Fri, Apr 28, 2023 at 8:32 AM Jerry D via Fortran > wrote: > > > > Hello all and gcc overseers, > > > > I received a notice that the MasterMost server providers decided to drop > > their free service.

Re: PR109439 - Terminate analysis path when OOB detected

2023-05-01 Thread Mark Wielaard
Hi Benjamin, On Mon, May 01, 2023 at 02:43:13PM +0200, Benjamin Priour via Gcc wrote: > I believe I still don't have the right to commit it directly to the repo, > and honestly even if I would using my fresh gcc account, I would prefer not > to commit it myself for the first patch, I don't wanna m

Re: More C type errors by default for GCC 14

2023-05-14 Thread Mark Wielaard
Hi Po, On Fri, May 12, 2023 at 09:53:30PM +0800, Po Lu via Gcc wrote: > I don't want anything, seeing as I've been using GCC less and less over > the years (for this and other reasons.) I'm just throwing in my two or > so cents. I think you have contributed more than two cents and it time to sto

Sourceware joins Software Freedom Conservancy

2023-05-15 Thread Mark Wielaard
https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/ After various discussions and lots of positive feedback [1] [2] [3] [4] Software Freedom Conservancy and Sourceware proudly announce that Sourceware today joins SFC as a member project! As the fiscal host of Sourceware, Software Fre

Re: Will GCC eventually support SSE2 or SSE4.1?

2023-05-26 Thread Mark Wielaard
Stefan, On Fri, 2023-05-26 at 14:22 +0200, Stefan Kanthak wrote: > "Jonathan Wakely" wrote: > > And when did you report it to bugzilla? > > > > Nobody reads your silly webpage. > > Thanks stupid. I don't read your silly bugzilla! Stop calling people stupid or dumbass. People are trying to hel

Re: Who cares about performance (or Intel's CPU errata)?

2023-05-27 Thread Mark Wielaard
Hi Stefan, On Sun, May 28, 2023 at 12:52:30AM +0200, Stefan Kanthak wrote: > >> Just to show how SLOPPY, INCONSEQUENTIAL and INCOMPETENT GCC's developers > >> are: This is totally not constructive. You should stop attacking others like that on this list. > OUCH, my fault; sorry for the confusio

Re: Imagination Technologies Limited - FSF copyright assignment forms

2023-06-08 Thread Mark Wielaard
Hi Ed, On Thu, Jun 08, 2023 at 10:32:15AM +, Ed Crothall wrote: > Could you please send across the relevant copyright assignment forms > to enable contributions to GCC from Imagination Technologies > Limited? At https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright you'll find the r

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-08 Thread Mark Wielaard
Hi Arsen, On Tue, Jun 06, 2023 at 08:43:05PM +0200, Arsen Arsenović via Gcc wrote: > IMO, the sparing usage of this power on what are clearly purely abusive > participants can only drive away users and contributors. It seems > reasonable to establish a process for dealing with incidents like this

Re: Network Services Alert#489707

2023-07-13 Thread Mark Wielaard
Hi Dave, On Wed, Jul 12, 2023 at 09:34:31AM -0500, Dave Blanchard wrote: > You know, if you useless cocksuckers [...] Please stop using this kind of language on this list. I know it is annoying if the spam filters didn't catch some obvious scam message. But you are not helping anybody by replyin

Re: Hundreds of gcc.dg/guality failures on both 14 and 13.1 branches

2023-07-16 Thread Mark Wielaard
Hi, On Sun, Jul 16, 2023 at 09:50:24AM +0200, FX Coudert via Gcc wrote: > > Which is why people should just compare testsuite results from earlier run > > on the same configuration to watch for regressions, especially in the > > guality testsuite. > > All this gives the idea of a test framework t

After Cauldron - online mini BoFs and Fosdem

2023-09-27 Thread Mark Wielaard
Hi all, Cauldron was really great. Seeing everybody in person again. One item that came up was about meeting more frequently and/or in smaller (virtual) groups. If people want to have online mini BoFs to follow up on some discussion they had at Cauldron, or for some periodic meetup, then please r

Sourceware Open Office, Friday October 13, 18:00 UTC

2023-10-11 Thread Mark Wielaard
Every second Friday of the month is the Sourceware Overseers Open Office hour in #overseers on irc.libera.chat from 18:00 till 19:00 UTC. That is this Friday October 13th. Please feel free to drop by with any Sourceware services and hosting questions. Some specific topics we will likely discuss:

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

2023-11-08 Thread Mark Wielaard
Hi Martin, On Mon, Nov 06, 2023 at 06:04:48PM +0100, Martin Jambor wrote: > I have inherited Martin Liška's buildbot script that checks that all > sorts of autotools generated files, mainly configure scripts, were > re-generated correctly when appropriate. While the checks are hopefully > useful,

Sourceware Open Office, Friday Novemer 10, 18:00 UTC

2023-11-08 Thread Mark Wielaard
Every second Friday of the month is the Sourceware Overseers Open Office hour in #overseers on irc.libera.chat from 18:00 till 19:00 UTC. That is this Friday October 10th. This time we will probably focus on integration of builder CI, Full, Try builds and patchwork PreCommit-CI. But please feel fr

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

2023-11-15 Thread Mark Wielaard
Hi! (adding gdb and binutils to the CC) On Thu, Nov 09, 2023 at 12:30:59AM +0100, Mark Wielaard wrote: > On Mon, Nov 06, 2023 at 06:04:48PM +0100, Martin Jambor wrote: > > I have inherited Martin Liška's buildbot script that checks that all > > sorts of autotools generated fil

Sourceware infrastructure updates for Q4 2023

2023-11-28 Thread Mark Wielaard
Sourceware infrastructure community updates for Q4 2023 - 6 months with the Software Freedom Conservancy - Sourceware @ Fosdem - OSUOSL provides extra larger arm64 and x86_64 buildbot servers - No more From rewriting for patches mailinglists = 6 months with the Software Freedom Conservancy Sourc

Re: libgcov, fork, and mingw (and other targets without the full POSIX set)

2023-12-07 Thread Mark Wielaard
Hi, On Fri, 2023-12-01 at 13:09 +0100, Jakub Jelinek via Gcc wrote: > On Fri, Dec 01, 2023 at 01:03:01PM +0100, Jan Hubicka via Gcc wrote: > > > On Dez 01 2023, Richard Biener via Gcc wrote: > > > > > > > Hmm, so why's it then referenced and not "GCed"? > > > > > > This has nothing to do with ga

Sourceware Open Office, Friday January 12, 18:00 UTC

2024-01-11 Thread Mark Wielaard
Happy new year! This Friday will be the first Sourceware Open Office of 2024. Join us this Friday, January 12, in #overseers on irc.libera.chat from 18:00 till 19:00 UTC. For any questions or ideas about any Sourceware service and/or integration of cgit, bugzilla, mailinglists, snapshots, mirror

Core Toolchain and Developer Tools at FOSDEM

2024-01-28 Thread Mark Wielaard
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 an

Sourceware Open Office, Friday February 9, 18:00 UTC

2024-02-08 Thread Mark Wielaard
Hi Sourceware projects hackers, 2024 started strong with various Sourceware core toolchain and developer tool projects presenting at Fosdem. If you missed the in person meetings, most talks have video recordings: https://fosdem.org/2024/schedule/track/debuggers-and-analysis/ https://fosdem.org/20

Re: Legal assignment forms for GCC

2024-02-22 Thread Mark Wielaard
Hi Robert, On Thu, Feb 22, 2024 at 02:29:03PM -0600, Robert Dubner wrote: > I anticipate making contributions to GCC on an ongoing basis, and > according to https://gcc.gnu.org/contribute.html, there are some forms > that need to be filled out by me and my employer for ".assignment.for all > futur

Sourceware infrastructure updates for Q1 2024

2024-02-27 Thread Mark Wielaard
Sourceware infrastructure community updates for Q1 2024 A summary of news about Sourceware, the Free Software hosting project for core toolchain and developer tools, from the last 3 months. - Sourceware now has an official donation page - StarFive VisionFive-2 RISC-V boards for builder.sourceware

Re: Help needed with maintainer-mode

2024-02-29 Thread Mark Wielaard
Hi Christophe, On Thu, Feb 29, 2024 at 11:22:33AM +0100, Christophe Lyon via Gcc wrote: > I've noticed that sourceware's buildbot has a small script > "autoregen.py" which does not use the project's build system, but > rather calls aclocal/autoheader/automake/autoconf in an ad-hoc way. > Should we

Re: Help needed with maintainer-mode

2024-03-01 Thread Mark Wielaard
Hi Christophe, On Thu, 2024-02-29 at 18:39 +0100, Christophe Lyon wrote: > On Thu, 29 Feb 2024 at 12:00, Mark Wielaard wrote: > > That python script works across gcc/binutils/gdb: > > https://sourceware.org/cgit/builder/tree/builder/containers/autoregen.py > > >

Re: Help needed with maintainer-mode

2024-03-03 Thread Mark Wielaard
Hi Christophe, On Fri, Mar 01, 2024 at 05:32:15PM +0100, Christophe Lyon wrote: > > > > And it was indeed done this way because that way the files are > > > > regenerated in a reproducible way. Which wasn't the case when using > > > > --enable-maintainer-mode (and autoreconfig also doesn't work).

Sourceware Open Office, Friday 18:00 UTC, don't feel isolated

2024-03-07 Thread Mark Wielaard
TL;DR; Friday March 8, 18:00 UTC, Sourceware Open Office discussion of services priorities for 2024, irc.liberachat.org #overseers To get the right time in your local timezone: $ date -d "Fri Mar 8 18:00:00 UTC 2024" In 2022 we published the Sourceware GNU Toolchain Infrastructure Roadmap [1]. An

Re: About gsoc

2024-03-11 Thread Mark Wielaard
Hi Dave, On Sun, Mar 10, 2024 at 08:17:31PM -0500, Dave Blanchard wrote: > > > On Tue, 5 Mar 2024 at 01:59, Dave Blanchard wrote: > > > > Wow, what a fucking prick this guy is. > > > > [...] > You are one of the biggest assholes I've encountered in the open > source world, and I've met some real

Sourceware 2024 - The Plan

2024-03-25 Thread Mark Wielaard
The Sourceware Project Leadership Committee in discussion with the Software Freedom Conservancy staff came up with the Sourceware 2024 plan and is looking at longer term projects that would be needed to keep your infrastructure running smoothly and securely for the next couple of years. We are curr

Re: GNU Tools Cauldron 2024

2024-03-29 Thread Mark Wielaard
On Wed, 2024-03-06 at 12:47 -0800, Bradley M. Kuhn via Gcc wrote: > Eric Gallager wrote: > > Hi, I would greatly appreciate a US option, and having it in Portland > > would be especially convenient for me, as then I could stay with > > family, so I would like to express my interest in it and would

Security warning about xz library compromise

2024-03-29 Thread Mark Wielaard
Sourceware hosts are not affected by the latest xz backdoor. But we have reset the https://builder.sourceware.org containers of debian-testing, fedora-rawhide and opensuse-tumbleweed. These containers however didn't have ssh installed, were running on isolated VMs on separate machines from our mai

Sourceware mitigating and preventing the next xz-backdoor

2024-04-01 Thread Mark Wielaard
A big thanks to everybody working this long Easter weekend who helped analyze the xz-backdoor and making sure the impact on Sourceware and the hosted projects was minimal. This email isn't about the xz-backdoor itself. Do see Sam James FAQ https://gist.github.com/thesamesam/223949d5a074ebc3dce9ee7

Re: Sourceware mitigating and preventing the next xz-backdoor

2024-04-04 Thread Mark Wielaard
Hi, On Wed, 2024-04-03 at 08:53 -0500, Joel Sherrill wrote: > On Wed, Apr 3, 2024, 3:09 AM Florian Weimer via Gdb > wrote: > > * Guinevere Larsen via Overseers: > > > > > Beyond that, we (GDB) are already experimenting with approved-by, and > > > I think glibc was doing the same. > > > > The g

Re: Sourceware mitigating and preventing the next xz-backdoor

2024-04-04 Thread Mark Wielaard
Hi, On Wed, 2024-04-03 at 08:42 -0600, Jeff Law wrote: > On 4/3/24 8:04 AM, Tom Tromey wrote: > > > > > > > "Florian" == Florian Weimer writes: > > > > Florian> Everyone still pushes their own patches, and there are no > > Florian> technical countermeasures in place to ensure that the pushed >

Re: Patches submission policy change

2024-04-04 Thread Mark Wielaard
Hi Christophe, On Wed, Apr 03, 2024 at 10:22:24AM +0200, Christophe Lyon via Gdb wrote: > TL;DR: For the sake of improving precommit CI coverage and simplifying > workflows, I’d like to request a patch submission policy change, so > that we now include regenerated files. This was discussed during

Re: Patches submission policy change

2024-04-06 Thread Mark Wielaard
Hi, On Fri, 2024-04-05 at 09:17 +0200, Christophe Lyon wrote: > On 4/4/24 23:35, Mark Wielaard wrote: > > wrt to the mailinglists maybe getting larger patches, I think most > > will still be under 400K and I wouldn't raise the limit (because most > > such larger emails

Re: Patches submission policy change

2024-04-07 Thread Mark Wielaard
Hi Jonathan, On Sun, Apr 07, 2024 at 01:32:11PM +0100, Jonathan Wakely via Gdb wrote: > On Thu, 4 Apr 2024, 22:36 Mark Wielaard, wrote: > > wrt to the mailinglists maybe getting larger patches, I think most > > will still be under 400K and I wouldn't raise the limit (because

Re: Patches submission policy change

2024-04-07 Thread Mark Wielaard
Hi Jonathan, On Sun, Apr 07, 2024 at 03:20:42PM +0100, Jonathan Wakely wrote: > On Sun, 7 Apr 2024, 15:02 Mark Wielaard, wrote: > > The jit mailinglist is the same. It only has one moderator > > (David). Having a second/backup one would probably be nice. Are you ok > &

Re: Sourceware mitigating and preventing the next xz-backdoor

2024-04-21 Thread Mark Wielaard
Hi Alejandro, On Wed, Apr 10, 2024 at 06:30:42PM +0200, Alejandro Colomar wrote: > It would also be interesting to require showing range-diffs between > patch revisions. They make it much more difficult to introduce a > vulnerability after a reviewer has turned its mins into approving the > patch

Re: Updated Sourceware infrastructure plans

2024-04-22 Thread Mark Wielaard
Hi Joseph, On Thu, 2024-04-18 at 15:56 +, Joseph Myers wrote: > On Thu, 18 Apr 2024, Mark Wielaard wrote: > > > But we like to get more feedback on what people really think a > > "pull-request" style framework should look like. We used to have a > > gerrit

Re: Updated Sourceware infrastructure plans

2024-04-23 Thread Mark Wielaard
Hi, On Mon, Apr 22, 2024 at 11:51:00PM -0400, Jason Merrill wrote: > On Mon, Apr 22, 2024 at 11:24 PM Tom Tromey wrote: > > Jason> Someone mentioned earlier that gerrit was previously tried > > Jason> unsuccessfully. > > > > We tried it and gdb and then abandoned it. We tried to integrate it > >

Re: Updated Sourceware infrastructure plans

2024-05-01 Thread Mark Wielaard
Hi Jonathan, On Wed, May 01, 2024 at 08:38:26PM +0100, Jonathan Wakely wrote: > On Wed, 1 May 2024 at 20:19, Jeff Law via Gcc wrote: > > We're currently using patchwork to track patches tagged with RISC-V. We > > don't do much review with patchwork. In that model patchwork ultimately > > just a

Re: Updated Sourceware infrastructure plans

2024-05-01 Thread Mark Wielaard
Hi Jason, On Wed, May 01, 2024 at 04:04:37PM -0400, Jason Merrill wrote: > On 5/1/24 12:15, Jeff Law wrote: > >We're currently using patchwork to track patches tagged with > >RISC-V.  We don't do much review with patchwork.  In that model > >patchwork ultimately just adds overhead as I'm constantl

Re: Updated Sourceware infrastructure plans

2024-05-02 Thread Mark Wielaard
Hi Jeff, On Wed, 2024-05-01 at 15:38 -0600, Jeff Law wrote: > What works well? If you've wired up some CI bits, it's is extremely > useful to test an under development patch. Develop, push a branch, > raise an MR. At that point the CI system kicks in. Subsequent pushes > to the branch trigg

Sourceware Open Office, Friday 16:00 UTC

2024-05-10 Thread Mark Wielaard
Friday May 10, 16:00 UTC, irc.libera.chat #overseers (Today in about 1 hour) To get the right time in your local timezone: $ date -d "Fri May 10 16:00:00 UTC 2024" Lots of discussion topics: - Sourceware 2024 - The Plan https://inbox.sourceware.org/20240325095827.gi5...@gnu.wildebeest.org/ - So

Re: Wrong date

2024-05-23 Thread Mark Wielaard
Hi Tony, On Wed, May 22, 2024 at 06:58:34PM -0500, tony.antonucci--- via Gcc wrote: > This was for the gcc 14.1 release. > Sorry I omitted that in the first email. Thanks for the notice, this has been fixed now: https://gcc.gnu.org/cgit/gcc-wwwdocs/commit/?id=465817d0e0a96a1e1722a67383183dbec95ab

Re: FSF copyright assignment

2024-05-25 Thread Mark Wielaard
Hi Seyed, On Sat, May 25, 2024 at 11:34:53AM +0100, Seyed Sajad Kahani via Gcc wrote: > I am writing to request the FSF copyright assignment forms, as they > are a legal requirement for contributing to GCC. At https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright you'll find the request

Re: Sourceware @ Conservancy - Year One

2024-05-30 Thread Mark Wielaard
Hi Maxim, On Thu, May 30, 2024 at 12:18:38PM +0400, Maxim Kuvyrkov via Overseers wrote: > > On May 29, 2024, at 23:02, Mark Wielaard wrote: > > And a special thanks to ARM who have been using > > https://patchwork.sourceware.org/ to provide a pre-commit testing > > serv

Re: gcc git locked out for hours second day in a row

2024-06-12 Thread Mark Wielaard
Hi, On Wed, 2024-06-12 at 13:48 +0200, Jakub Jelinek via Gcc wrote: > Yesterday the gcc git repository was locked for 3 hours > locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167) > 78:06 python hooks/update.py > refs/users/mikael/tags/fortran-dev_merges/r10-1545 > 000

Sourceware Open Office, Friday 16:00 UTC

2024-06-12 Thread Mark Wielaard
Friday June 14, 16:00 UTC, irc.libera.chat #overseers To get the right time in your local timezone: $ date -d "Fri May 10 16:00:00 UTC 2024" - Discussion topic: https://sourceware.org/sourceware-security-vision.html The Sourceware infrastructure security vision explains what Sourceware is

unwanted communication

2024-06-30 Thread Mark Wielaard
Dear Shendung Wang, You have been misbehaving and sending threatening messages to various gcc mailinglist and have posted such messages in bugzilla under the euloanty or cqwrteur handle. You should immediately stop that. Thanks, Mark

Re: Bad interaction between gcc and glibc's handling of GNU extension [GCC PR 115724]

2024-07-02 Thread Mark Wielaard
Hi David, On Tue, Jul 02, 2024 at 03:57:58PM -0400, David Malcolm wrote: > > > At -O0 sure, that is how __builtin_constant_p works. > > > The above is intended for optimized compilation, and I think it > > > works just fine then. > > > > And it's generally needed with optimization only, to suppre

Sourceware Open Office, Friday 16:00 UTC

2024-07-09 Thread Mark Wielaard
Friday July 12, 16:00 UTC https://bbb.sfconservancy.org/b/mar-aom-dmo-fko Using #overseers on irc.libera.chat as backup. To get the right time in your local timezone: $ date -d "Fri Jul 12 16:00 UTC 2024" Sourceware relies on cooperation among a broad diversity of core toolchain and developer too

RISC-V Pioneer Box for builder.sourceware.org gcc CI

2024-08-01 Thread Mark Wielaard
Hi, Thanks to RISC-V International and SOPHGO we got a Milk-V Pioneer Box [*] for builder.sourceware.org that we can use for gcc CI. It is running Fedora 38 with gdb 15.1, binutils 2.42 and gcc 14.1 installed on top. We could create containers with other setups if useful. https://builder.sourcew

Re: RISC-V Pioneer Box for builder.sourceware.org gcc CI

2024-08-05 Thread Mark Wielaard
Hi, On Thu, Aug 01, 2024 at 11:07:20PM +0200, Mark Wielaard wrote: > Thanks to RISC-V International and SOPHGO we got a Milk-V Pioneer Box > [*] for builder.sourceware.org that we can use for gcc CI. > > It is running Fedora 38 with gdb 15.1, binutils 2.42 and gcc 14.1 > insta

Re: RISC-V Pioneer Box for builder.sourceware.org gcc CI

2024-08-08 Thread Mark Wielaard
Hi, On Tue, Aug 06, 2024 at 02:11:45PM -0600, Jeff Law wrote: > On 8/6/24 1:50 PM, Florian Weimer wrote: > >* Jeff Law via Gcc: > > > >>On 8/5/24 4:23 PM, Mark Wielaard wrote: > >> > >>>It was suggested to just ignore the machine has rvv since i

Sourceware Open Office, Friday 16:00 UTC

2024-08-08 Thread Mark Wielaard
Friday Aug 9, 16:00 UTC https://bbb.sfconservancy.org/b/mar-aom-dmo-fko Using #overseers on irc.libera.chat as backup. To get the right time in your local timezone: $ date -d "Fri Aug 9 16:00 UTC 2024" Sourceware relies on cooperation among a broad diversity of core toolchain and developer tool p

Re: RISC-V Pioneer Box for builder.sourceware.org gcc CI

2024-08-11 Thread Mark Wielaard
Hi Jeff, On Thu, Aug 08, 2024 at 09:51:24AM -0600, Jeff Law wrote: > On 8/8/24 9:13 AM, Mark Wielaard wrote: > >But I don't fully understand how the gcc testsuite detects whether rvv > >is implemented. e.g. rvv.exp seems to just check whether the target is > >RISC-V a

Re: Commit missing from gcc-cvs and bugzilla

2024-08-12 Thread Mark Wielaard
Hi Johann, On Sat, Aug 10, 2024 at 07:34:09PM +0200, Georg-Johann Lay wrote: > I just noticed that one of my commits, > > https://gcc.gnu.org/r15-2865 > > is missing from > > https://gcc.gnu.org/pipermail/gcc-cvs/2024-August/date.html > > Even though it has the tag "PR target/113934" the respe

Re: Forms for copyright assignment

2024-08-13 Thread Mark Wielaard
Hi Konstantinos, On Tue, Aug 13, 2024 at 11:12:17AM +0300, Konstantinos Eleftheriou wrote: > I would like to contribute to Binutils, GCC, glibc and GDB. Could > you send me the relevant forms for copyright assignment? My > contributions will be on behalf of VRULL. At https://git.savannah.gnu.org/

Re: gcc.gnu.org performance issues?

2024-08-15 Thread Mark Wielaard
Hi, On Thu, Aug 15, 2024 at 10:31:12AM -0700, H.J. Lu via Gcc wrote: > On Thu, Aug 15, 2024 at 10:17 AM Harald Anlauf via Gcc > wrote: > > is it only me who is recently experiencing intermittent > > but extreme slowness of "git pull"? > > > > I did an ssh -v and saw the following: > > > > debug1

Sourceware Open Office Friday and Cauldron Monday

2024-09-12 Thread Mark Wielaard
We'll have our regular Sourceware Open Office this Friday Sep 13, 16:00 UTC Using #overseers on irc.libera.chat To get the right time in your local timezone: $ date -d "Fri Sep 13 16:00 UTC 2024" Then at the Cauldron https://gcc.gnu.org/wiki/cauldron2024 in Prague on Monday at 11:00 local time we

Merging GNU Classpath and gcc/libgcj bug databases

2005-02-14 Thread Mark Wielaard
e reported through the gcc bugdatase. So sharing the bug database architecture/backend with the GCC project makes a lot of sense. By having it as a separate project we hope to also facilitate the other free compilers and runtimes based on GNU Classpath. Cheers, Mark Wielaard GNU Classpath Maintaine

Re: Merging GNU Classpath and gcc/libgcj bug databases

2005-02-14 Thread Mark Wielaard
Hi Chris, On Mon, 2005-02-14 at 19:50 +, Chris Burdess wrote: > What's the plan for auxiliary classpath modules such as inetlib and > cp-tools? Are they still managed in the Savannah bug tracker? The current plan is to also move them over and assign them separate categories/modules in the ne

Re: dwz-0.1 - DWARF compression tool

2012-04-18 Thread Mark Wielaard
On Wed, Apr 18, 2012 at 02:26:45PM +0200, Jakub Jelinek wrote: > Of course there is a lot of DWARF duplication in between different > libraries, or binaries, or e.g. Linux kernel modules (which have the > added problem that they have relocations against the sections; we could > apply and remove the

Sourceware forge experiment

2024-10-20 Thread Mark Wielaard
As an experiment Sourceware is now running an forgejo v9 instance at https://forge.sourceware.org Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org address can register an account (please use the same user name as your account name). The setup has disabled most "extras" (no badges, s

Sourceware Open Office Friday 16:00 UTC, A forge experiment?

2024-10-10 Thread Mark Wielaard
Friday Oct 11, 16:00 UTC https://bbb.sfconservancy.org/b/mar-aom-dmo-fko Using #overseers on irc.libera.chat as backup. To get the right time in your local timezone: $ date -d "Fri Oct 11 16:00 UTC 2024" Sourceware relies on cooperation among a broad diversity of core toolchain and developer tool

Re: Core Toolchain Infrastructure - October 2024 update

2024-10-30 Thread Mark Wielaard
Hi Carlos, On Tue, Oct 29, 2024 at 06:02:03PM -0400, Carlos O'Donell via Gcc wrote: > Recent discussions on the glibc mailing list make it clear > that we need to expand and discuss more about our "why" along with > the "what" and "how" of these changes. Zoe wrote a good summary of that discussio

Re: Core Toolchain Infrastructure - October 2024 update

2024-11-04 Thread Mark Wielaard
Hi Carlos, On Wed, Oct 30, 2024 at 12:52:13PM -0400, Carlos O'Donell wrote: > > We discussed this with OpenSSF and submitted a funding request to > > OpenSSF Alpha Omega for this particular part. OpenSSF initially was > > supportive to funding these kinds of security plans, but they have been > >

Re: Core Toolchain Infrastructure - October 2024 update

2024-10-30 Thread Mark Wielaard
Hi Carlos, On Wed, 2024-10-30 at 08:32 -0400, Carlos O'Donell wrote: > I can get down to specific requirements and possible solutions for them, > including > things like securing logins with 2FA etc. Which *could* be solved by > Sourceware > today possibly using Nitrokeys (open hardware and FOSS

Sourceware infrastructure updates for Q3 2024

2024-09-30 Thread Mark Wielaard
Sourceware infrastructure community updates for Q3 2024 Sourceware has provided the infrastructure for the core toolchain and developer tools for more than 25 years. https://sourceware.org/sourceware-25-roadmap.html The last couple of years it has transformed from a purely volunteer into a profes

Sourceware Open Office Friday 16:00 UTC, A forge experiment!

2024-11-06 Thread Mark Wielaard
Friday Nov 8, 16:00 UTC https://bbb.sfconservancy.org/b/mar-aom-dmo-fko Using #overseers on irc.libera.chat as backup. To get the right time in your local timezone: $ date -d "Fri Nov 8 16:00 UTC 2024" Sourceware relies on cooperation among a broad diversity of core toolchain and developer tool p

Re: Sourceware forge experiment

2024-11-08 Thread Mark Wielaard
Hi Eric, On Thu, 2024-10-24 at 15:44 -0400, Eric Gallager wrote: > On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard wrote: > > As an experiment Sourceware is now running an forgejo v9 instance at > > https://forge.sourceware.org > > > > Everybody with an @sou

Re: Align the gcc, glibc, and binutils DCO text to match community usage.

2024-11-24 Thread Mark Wielaard
; than a known identity that could be contacted to discuss the > contribution (and what was attested). > > The same changes have been made to other projects including as noted > by Sam James in the Gentoo project [2], Mark Wielaard in elfutils [3], > and CNCF [4]. It should probably b

Sourceware Cyber Security FAQ

2024-11-27 Thread Mark Wielaard
ute (security issues) back upstream. So any policies documenting how to clearly report issues and documenting the contributing and release practices should be helpful. Please let us know if you have any questions or suggestions. Cheers, Mark Wielaard (for the Sourceware PLC) https://sourceware.org/mission.html#plc

Re: Sourceware Cyber Security FAQ

2024-11-27 Thread Mark Wielaard
Hi Jeffrey, On Wed, Nov 27, 2024 at 12:27:14PM -0500, Jeffrey Walton wrote: > On Wed, Nov 27, 2024 at 11:35 AM Mark Wielaard wrote: > > After lots of discussions at some of our Open Office hours, at the > > Cauldron, with other Software Freedom organizations and some of our &

Re: libdiagnostics name clash

2024-11-20 Thread Mark Wielaard
On Wed, Nov 20, 2024 at 04:11:16PM -0500, David Malcolm via Gcc wrote: > I merged libdiagnostics to GCC trunk on Monday: > https://gcc.gnu.org/wiki/libdiagnostics > > Unfortunately I've since discovered there's at least one libdiagnostics > .so already in Debian: > https://tracker.debian.org/pkg

Re: commits and bugzilla

2024-11-16 Thread Mark Wielaard
Hi Martin, On Sat, Nov 16, 2024 at 10:03:41AM +0100, Martin Uecker via Gcc wrote: > I just commited a bug fix and noticed that bugzilla was > not automatically updated. > > https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=d8af6c203f18b4fd736df9567926589d96f8e0b3 > > Did something change / break or

Re: We need to remove the Sphinx HTML docs

2024-11-15 Thread Mark Wielaard
Hi, On Fri, 2024-11-15 at 12:14 +, Jonathan Wakely via Gcc wrote: > On IRC mjw suggested that you (Gerald) might object to breaking links > by just removing them. I think the pages are already broken (the links > in the sidebar are half missing already). > > If we think preserving those links

Re: Align the gcc, glibc, and binutils DCO text to match community usage.

2024-12-02 Thread Mark Wielaard
Hi Bradley, Thanks for following the discussion and your input. We have also been discussing some policy wording changes on gcc-patches: https://inbox.sourceware.org/gcc-patches/20241202101600.1041524-1-m...@klomp.org/T If you have any suggestions for improving the actual wording change that woul

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

2024-12-02 Thread Mark Wielaard
ting > > That did the job, thank you! > > On Sun, 1 Dec 2024, Mark Wielaard wrote: > > > > If that doesn't work we'll have to clean it up on the server. > > I believe things are fine? > > % git branch -la | cat > * master > remotes

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

2024-12-01 Thread Mark Wielaard
Hi Gerald, On Sun, Dec 01, 2024 at 07:26:45PM +0100, Gerald Pfeifer wrote: > On Fri, 23 Aug 2024, Eric Gallager wrote: > >>> The branch, python-formatting has been created > >>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit) > >> Hmm, are you intentionally creating a branch for the

Re: Patch held up in gcc-patches due to size

2025-02-03 Thread Mark Wielaard
Hi Thomas, On Sun, Feb 02, 2025 at 07:09:14PM +0100, Thomas Koenig via Gcc wrote: > I sent https://gcc.gnu.org/pipermail/fortran/2025-February/061670.html > to gcc-patches also, as normal, but got back an e-mail that it > was too large. and that a moderator would look at it. I think that was done

<    1   2   3   >