public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@arm.com>
Cc: buildbot@sourceware.org
Subject: Re: Arm GCC buildbot workers
Date: Wed, 17 Aug 2022 22:42:23 +0200	[thread overview]
Message-ID: <Yv1Sr84AcIiIMVpm@wildebeest.org> (raw)
In-Reply-To: <01b98c46-e1cd-e463-ee0c-88b26db76242@arm.com>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Hi Christophe,

On Wed, Aug 17, 2022 at 03:45:07PM +0200, Christophe Lyon wrote:
> > Currently the configure line is shared by all gcc-full builders. But
> > that can be changed. As in the attached patch (apologies for my python
> > skills). I'll push it once I have internet access again.
> 
> In case you have missed my follow-up message, the buildbot patch is not
> needed anymore: I pushed a fix in GCC instead :-)

Yes, sorry. I am on vacation in the mountains with spotty interweb
access, so sending/receiving emails in batches. Our emails crossed.

I like your gcc patch very much. It is much better if configure does
the right thing by default.

I removed the extra configure argument for the
gcc_full_ubuntu_armhf_builder. But kept the generator function just in
case we do want to have different configure arguments per builder in
the future.

Cheers,

Mark

[-- Attachment #2: 0001-Remove-with-float-hard-for-gcc_full_ubuntu_armhf_bui.patch --]
[-- Type: text/x-diff, Size: 964 bytes --]

From f4711d650a5f706d599a3122e6e54ca4f2cc2286 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Wed, 17 Aug 2022 22:39:28 +0200
Subject: [PATCH] Remove --with-float=hard for gcc_full_ubuntu_armhf_builder

gcc configure should now do the right thing automatically.
---
 builder/master.cfg | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/builder/master.cfg b/builder/master.cfg
index dc51fd0..318adad 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -3033,8 +3033,7 @@ gcc_full_ubuntu_armhf_builder = util.BuilderConfig(
         collapseRequests=True,
         workernames=["ubuntu22_04-armhf"],
         tags=["gcc-full", "ubuntu", "armhf"],
-        factory=gcc_full_build_factory_gen(
-                extra_configure_arg="--with-float=hard"))
+        factory=gcc_full_build_factory_gen())
 c['builders'].append(gcc_full_ubuntu_armhf_builder)
 
 gcc_full_ubuntu_arm64_builder = util.BuilderConfig(
-- 
2.30.2


      reply	other threads:[~2022-08-17 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  7:54 Christophe Lyon
2022-08-11 20:39 ` Mark Wielaard
2022-08-12  7:23   ` Christophe Lyon
2022-08-12 16:44     ` Mark Wielaard
2022-08-16 11:54       ` Christophe Lyon
2022-08-17 11:51         ` Christophe Lyon
2022-08-17 13:00         ` Mark Wielaard
2022-08-17 13:45           ` Christophe Lyon
2022-08-17 20:42             ` Mark Wielaard [this message]

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=Yv1Sr84AcIiIMVpm@wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=christophe.lyon@arm.com \
    /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).