public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] gas: copy st_size only if unset
Date: Fri, 8 Apr 2022 22:29:37 -0600	[thread overview]
Message-ID: <1fa4b802-97ef-9a6a-c107-0d4ba6f37662@gmail.com> (raw)
In-Reply-To: <20220408212613.inzusw2b2eved25p@gmail.com>



On 4/8/2022 3:26 PM, Fangrui Song wrote:
>
>
>
> PS: is there a shortcut than building all-binutils/all-gas with various
> different --target= (especially these exotic ones like
> alpha/hppa/nds32)?
Not really.    But you can head to the upstream GCC tester and grab log 
files.  It happens to also test binutils on a variety of targets.

The tester recently moved out of AWS back to a machine I host.  So the 
redirect from the gcc web pages needs updating.   Anyway, point your 
browser here:

http://law-sandy.freeddns.org:8080/job/nds32le-elf/

 From that page we see that the build on April 5 was good and the build 
on April 6 was bad.  It flipped back to green today as I told the system 
generate new baselines for the nds targets as I'm primarily interested 
in catching GCC regressions.

You can dig into the log files to get the git hashes in use.  I use 
those to see my bisections when I need to chase something down.

Anyway, thought you might find it useful.

Jeff




      parent reply	other threads:[~2022-04-09  4:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31  3:37 Fangrui Song
2022-03-31  6:22 ` Jan Beulich
2022-04-01  1:33   ` Fangrui Song
2022-04-04 11:27     ` Jan Beulich
2022-04-08  7:42     ` Alan Modra
2022-04-08 21:26       ` Fangrui Song
2022-04-08 23:01         ` Fangrui Song
2022-04-08 23:06           ` Fangrui Song
2022-04-09  1:12           ` Alan Modra
2022-04-09  0:43         ` Alan Modra
2022-04-09  4:29         ` Jeff Law [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=1fa4b802-97ef-9a6a-c107-0d4ba6f37662@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=binutils@sourceware.org \
    /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).