From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 7F1E83858D1E for ; Tue, 3 Jan 2023 10:08:53 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1672740532; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bJyiJ/eDsSnqu9y0SqAJ+D1Pcn7J9R8eqltGG4mA0Ts=; b=T7HzK2rXd5QQz7gq4m/o0q2nUtshMjpbYV0LyfOQ6cctvPRfGl8uilBQUUsr6wA5FzvoH2 31uXVLaQ3wL/tgOTRLmmWKWG5DVTqi2nvRMQ8suGirv4EM5m418zmTRJ8Nvx8Mtmmf0UWn /pQ7ftdZmfix5wxRGeQqZjXRgwlWXPk= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-29-QGx45hWvMCmwb2cPEFW1Nw-1; Tue, 03 Jan 2023 05:08:51 -0500 X-MC-Unique: QGx45hWvMCmwb2cPEFW1Nw-1 Received: by mail-wm1-f71.google.com with SMTP id q21-20020a7bce95000000b003d236c91639so6725388wmj.8 for ; Tue, 03 Jan 2023 02:08:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=bJyiJ/eDsSnqu9y0SqAJ+D1Pcn7J9R8eqltGG4mA0Ts=; b=uCLs00Sg4jzhDyNpfuJGSMeL5xEKWO0s/8y/xADM55bgdQBZizsoVjK6Ds2XyRW0kJ Hrr3QZkspMrStyIQdT1DoWWxq0f12uaqzhvcMjGS1e+oGmf9e4IClPUqQXyTSykVIR2a azHIOVYO1lMCKmKJ4ntnT9Wek4tSBg//xZvwcaBXBadj46SVWGvFmNygVQAbRnHYsBbq sNbdy+ZapACqNtYNOouXDhsk2wWzrvvDKnk/vkxywoc6eihfdeDV/m74DdhE6JOPIYXK 6nKu9G5V+V6zW+qqhWAqhWi9F3Wu0aIvwpJZOtmnOvFEODDezaXE4QMFXwqHjfm1rTT1 A+7A== X-Gm-Message-State: AFqh2kqvRZV+ZBCcIIt1zwVUeRYdGdjB6a9oSr28PcipeKZIE1VZMeIO stIWQTMBYUK2TIKuEontEk1Gcaqp8ZkbeInHFBTKcHzAco5eFITQs7JbMKX80pq2EWEJYex/JmW 1h6zhTwoeHnFwrFHfHw== X-Received: by 2002:a05:600c:4e08:b0:3cf:d0b1:8aa1 with SMTP id b8-20020a05600c4e0800b003cfd0b18aa1mr30546000wmq.0.1672740530620; Tue, 03 Jan 2023 02:08:50 -0800 (PST) X-Google-Smtp-Source: AMrXdXv96WYJHYs6UZjNw6Z4l8gvFJJHbDpBu1TWVMEf1VynV5c7t1vJxGCGD5nOuF9J7E9BzuZy7g== X-Received: by 2002:a05:600c:4e08:b0:3cf:d0b1:8aa1 with SMTP id b8-20020a05600c4e0800b003cfd0b18aa1mr30545987wmq.0.1672740530370; Tue, 03 Jan 2023 02:08:50 -0800 (PST) Received: from [192.168.1.18] ([79.123.75.206]) by smtp.gmail.com with ESMTPSA id w23-20020a1cf617000000b003d9b89a39b2sm5470921wmc.10.2023.01.03.02.08.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Jan 2023 02:08:49 -0800 (PST) Message-ID: <2b64a6ff-4e3b-e5e4-0e8b-910821d4390d@redhat.com> Date: Tue, 3 Jan 2023 10:08:48 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 To: Mark Wielaard Cc: joel@rtems.org, Mike Frysinger , Joel Brobecker , Binutils References: <71067e2b-f43b-2be8-ea4a-88ead1dd6e56@redhat.com> <4ca81bcb-c569-7d9d-a243-fea12bfead52@redhat.com> <87fb1712-d568-46fc-aa47-733ff6931171@redhat.com> <4944644e-68c3-abfa-e2dd-e99bcb4085f0@redhat.com> From: Nick Clifton Subject: Re: A GNU Binutils wiki In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-GB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Mark, >>> How are the current code snapshots created? >> >> I think that there is a cron job on sourceware that creates the snapshots. > > I can find the gdbadmin cron job that creates gdb snapshots, but it > looks like you create the binutils snapshots by hand and upload them > to https://sourceware.org/pub/binutils/snapshots/ Ah - yes - that does indeed appear to be the case. I think that in the past there was a cron job that would create daily snapshots, but I guess that it went away. > It would be nice to automate this a bit more either with a real > cronjob or a specific buildbot worker. I would be happy for that to happen. Can I just say "pretty please" ? or do you need me to do something ? > About > > 12. Build various different toolchains, test them and nag > maintainers to fix any testsuite failures for their > architectures... > > Which toolchains/architectures are that? Are any of them missing from: > https://builder.sourceware.org/buildbot/#/builders?tags=binutils Lots! I build about 100 different combinations in my local test farm. Most are slightly obscure configurations or targets however, so I would not worry too much about them. There are a few that would be nice to see added to your buildbot farm however, should you have the capacity: aarch64-linux-gnu mipsel-linux-gnu riscv64-elf >>> We can automate both and publish them on a special buildbot worker >>> under something like snapshots.sourceware.org/bintuils to keep them >>> current and so everybody can immediately see how the documentation >>> looks. >> >> That would be nice. Would it involve taking up a lot of disk space ? >> (Ie for how long would these snapshots last ?) > > binutils snapshots are ~24MB, documentation ~18MB. So if we do one a > day that is ~1GB a month. And since it looks like you recently added > the option to create reproducible tarballs we don't really need to > keep all of them since people could recreate them from a git checkout. That makes sense. So if you are willing to make it happen that would be grand. Cheers Nick