From: Nick Clifton <nickc@redhat.com>
To: binutils@emagii.com, binutils@sourceware.org
Cc: Ulf Samuelsson <ulf@emagii.com>
Subject: Re: [PATCH v11 04/11] DIGEST: testsuite
Date: Mon, 6 Mar 2023 12:27:48 +0000 [thread overview]
Message-ID: <c8ac36b3-3cbc-a26d-d122-6b2266ca818e@redhat.com> (raw)
In-Reply-To: <20230303144706.1977061-5-binutils@emagii.com>
Hi Ulf,
Unfortunately I am seeing some new failures with these tests for
various different targets:
tic4x-coff, tic54x-cof:
LD REGRESSION: ld-scripts/crc64-reverse-area
LD REGRESSION: ld-scripts/crc64-in-section
These appear to be due to the test case being too big for the target:
./ld-new: error: tmpdir/dump(.text) is too large (0x2050 bytes)
./ld-new: '&s' section contents unavailable
CRC generation aborted
I suggest that either you make the .text sections smaller, or skip
these tests for the above targets.
ns32k-pc532-macho, pdp11-dec-aout, powerpc-ibm-aix5.2.0, rs6000-aix4.3.3, alpha-linuxecoff:
LD REGRESSION: ld-scripts/crc64-reverse-area
LD REGRESSION: ld-scripts/crc64-in-section
LD REGRESSION: ld-scripts/crc64-same-section
LD REGRESSION: ld-scripts/crc64-multiple-digest
LD REGRESSION: ld-scripts/crc64-unknown-digest
LD REGRESSION: ld-scripts/crc64-poly-size
LD REGRESSION: ld-scripts/crc64-bad-label
LD REGRESSION: ld-scripts/crc64-bad-label-2
LD REGRESSION: ld-scripts/crc64-bad-endian-size
LD REGRESSION: ld-scripts/crc64-bad-endian-contents
example failure messages:
Error: unknown pseudo-op: `.section'
and:
the XCOFF file format does not support arbitrary sections
These are all because these particular file formats do not support
the .section assembler directive. I suggest that you add some
#skip ... directives to the associated .d test driver files.
Cheers
Nick
next prev parent reply other threads:[~2023-03-06 12:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 14:46 [PATCH v11 0/11 Add support for CRC64 generation in linker binutils
2023-03-03 14:46 ` [PATCH v11 01/11] DIGEST: LICENSING binutils
2023-03-03 14:46 ` [PATCH v11 02/11] DIGEST: NEWS binutils
2023-03-03 14:46 ` [PATCH v11 03/11] DIGEST: Documentation binutils
2023-03-03 14:46 ` [PATCH v11 04/11] DIGEST: testsuite binutils
2023-03-06 12:27 ` Nick Clifton [this message]
2023-03-06 13:18 ` Ulf Samuelsson
2023-03-03 14:47 ` [PATCH v11 05/11] DIGEST: ldlex.l binutils
2023-03-03 14:47 ` [PATCH v11 06/11] DIGEST: ldgram.y binutils
2023-03-03 14:47 ` [PATCH v11 07/11] DIGEST: ldmain.c binutils
2023-03-03 14:47 ` [PATCH v11 08/11] DIGEST: ldlang.*: add timestamp binutils
2023-03-03 14:47 ` [PATCH v11 09/11] DIGEST: calculation binutils
2023-03-03 14:47 ` [PATCH v11 10/11] DIGEST: Makefile.* binutils
2023-03-03 14:47 ` [PATCH v11 11/11] Build ldint binutils
2023-03-03 15:12 ` [PATCH v11 0/11 Add support for CRC64 generation in linker Ulf Samuelsson
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=c8ac36b3-3cbc-a26d-d122-6b2266ca818e@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@emagii.com \
--cc=binutils@sourceware.org \
--cc=ulf@emagii.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).