public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: binutils@sources.redhat.com
Cc: "'Jan Beulich'" <JBeulich@novell.com>
Subject: Re: [PATCH] gas should honor original section type (was Re:ELF	section identification and gld)
Date: Mon, 27 Sep 2004 16:33:00 -0000	[thread overview]
Message-ID: <415841AB.7040200@redhat.com> (raw)
In-Reply-To: <20040910135746.GH2695@bubble.modra.org>

Hi Guys,

>>>From: binutils-owner On Behalf Of Jan Beulich
>>>(in the architecture independent parts), is there any mechanism to
>>>build/test all (default) architectures without having to 
>>>manually build them individually?

As has already been said the only real mechanism to test the 
architecture independent parts of the tools is the brute force approach 
- build and check as many different targets as you can and look for 
regressions.


> Alan Modra wrote:
> I use the following script
> 
> for z in a29k-coff alpha-linuxecoff alpha-linux arc-elf arm-aout arm-coff arm-linux avr-elf cris-elf d10v-elf d30v-elf dlx-elf fr30-elf frv-elf hppa-linux hppa64-linux h8300-rtems h8300-elf h8500-rtems i370-linux i586-coff i586-aout i586-linux i686-pe i860-stardent-elf i960-intel-nindy i960-coff i960-elf ia64-linux ip2k-elf m32r-elf m68hc11-elf m68hc12-elf m68k-aout m68k-netbsd m68k-coff m68k-linux m88k-coff mcore-elf mcore-pe mips-ecoff mips-linux mmix mn10200-elf mn10300-elf openrisc-elf or32-coff or32-elf pj-elf powerpc-linux powerpc64-linux rs6000-aix4.3.3 rs6000-aix5.1 s390x-linux s390-linux sh-linux sh-pe sh-rtems sh64-elf ns32k-netbsd sparc-aout sparc-coff sparc-linux sparc64-linux tic30-unknown-aout tic30-unknown-coff tic4x-coff tic54x-coff tic80-coff v850-elf vax-netbsdelf vax-netbsd vax-vms w65-unknown-coff x86_64-linux xstormy16-elf z8k-coff

Interesting script.  I use makefiles myself but to a similar effect. 
There were several targets in your list which I was not testing, so I 
have added them to my framework.  I also noticed that your list does not 
include these targets which you might want to add: crx-elf, iq2000-elf, 
msp430-elf and xtensa-elf.

Cheers
   Nick


  reply	other threads:[~2004-09-27 16:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  6:44 [PATCH] gas should honor original section type (was Re: ELF " Jan Beulich
2004-09-10  9:49 ` [PATCH] gas should honor original section type (was " Dave Korn
2004-09-10 13:57   ` Alan Modra
2004-09-27 16:33     ` Nick Clifton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-15 10:15 [PATCH] gas should honor original section type (was Re: ELF " Jan Beulich
2004-12-16 12:12 ` Nick Clifton
2004-08-30  6:40 Jan Beulich
2004-09-09 11:10 ` Nick Clifton

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=415841AB.7040200@redhat.com \
    --to=nickc@redhat.com \
    --cc=JBeulich@novell.com \
    --cc=binutils@sources.redhat.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).