Re: Patches submission policy change
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 most > such larger emails are really just spam). But we might want to get > more mailinglist moderators. > > gcc-patches, binutils and gdb-patches all have only one moderator > (Jeff, Ian and Thiago). It would probably be good if there were > more. > > Any volunteers? It shouldn't be more than 1 to 3 emails a week > (sadly most of them spam). > > Cheers, > > Mark > I'm happy to help moderating/spambusting for the GCC lists.
Re: Patches submission policy change
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 most > > such larger emails are really just spam). But we might want to get > > more mailinglist moderators. > > > > gcc-patches, binutils and gdb-patches all have only one moderator > > (Jeff, Ian and Thiago). It would probably be good if there were > > more. > > > > Any volunteers? It shouldn't be more than 1 to 3 emails a week > > (sadly most of them spam). > > I'm happy to help moderating/spambusting for the GCC lists. I see you are already doing that for the libstdc++ mailinglist, but you are the only moderator. Maybe you want someone as backup there? The jit mailinglist is the same. It only has one moderator (David). Having a second/backup one would probably be nice. Are you ok to be added there? (I see that both the libstdc++ and jit mailinglist just allow up to 5MB patches, which probably means they don't block any legitimate ones, but might get a bit more spam than necessary). It isn't a patches mailinglist, so slightly less urgent, but the gcc-help mailinglist doesn't have any moderators. Would you be willing to help out with that one? Thanks, Mark
Re: Patches submission policy change
On Sun, 7 Apr 2024, 15:02 Mark Wielaard, wrote: > 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 most > > > such larger emails are really just spam). But we might want to get > > > more mailinglist moderators. > > > > > > gcc-patches, binutils and gdb-patches all have only one moderator > > > (Jeff, Ian and Thiago). It would probably be good if there were > > > more. > > > > > > Any volunteers? It shouldn't be more than 1 to 3 emails a week > > > (sadly most of them spam). > > > > I'm happy to help moderating/spambusting for the GCC lists. > > I see you are already doing that for the libstdc++ mailinglist, but > you are the only moderator. Maybe you want someone as backup there? > It wouldn't hurt to have backup if somebody wants to volunteer, but I don't remember ever having to moderate anything for that list. Maybe just once. > The jit mailinglist is the same. It only has one moderator > (David). Having a second/backup one would probably be nice. Are you ok > to be added there? > Sure! I imagine that one is quiet as well. > (I see that both the libstdc++ and jit mailinglist just allow up to > 5MB patches, which probably means they don't block any legitimate > ones, but might get a bit more spam than necessary). > > It isn't a patches mailinglist, so slightly less urgent, but the > gcc-help mailinglist doesn't have any moderators. Would you be willing > to help out with that one? > Sure, I'm subscribed and active there anyway.
Re: Patches submission policy change
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 > > to be added there? > > Sure! I imagine that one is quiet as well. Yes, we like quiet :) It means the spam filters work correctly. > > (I see that both the libstdc++ and jit mailinglist just allow up to > > 5MB patches, which probably means they don't block any legitimate > > ones, but might get a bit more spam than necessary). > > > > It isn't a patches mailinglist, so slightly less urgent, but the > > gcc-help mailinglist doesn't have any moderators. Would you be willing > > to help out with that one? > > Sure, I'm subscribed and active there anyway. Thanks for volunteering, you have been added to both as admin. Cheers, Mark
gcc-14-20240407 is now available
Snapshot gcc-14-20240407 is now available on https://gcc.gnu.org/pub/gcc/snapshots/14-20240407/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 14 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch master revision 4e3c8257304c55f2ebfb24bd6de3236bda0f054e You'll find: gcc-14-20240407.tar.xz Complete GCC SHA256=d7cbaf70ea1ed541c8da56979637fcd33181459f58217376ca7495a60ed0aa65 SHA1=f388be1f736d174690373e3b5e7414018cf8 Diffs from 14-20240331 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-14 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Problems when building NT kernel drivers with GCC / LD
On Sunday 07 January 2024 02:55:09 Pali Rohár wrote: > Hello, I would like to remind that the first gcc bug from the list in > previous email has not received any comment yet. It is this one: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108849 > Do you need some more details, or something else for it? Hello, I put comment in that bug report. Can you look at it?
