From: Xi Ruoyao <xry111@xry111.site>
To: binutils@sourceware.org, Lulu Cai <cailulu@loongson.cn>,
mengqinggang <mengqinggang@loongson.cn>
Subject: ld 2.42 test failures with GCC 14
Date: Fri, 02 Feb 2024 04:38:14 +0800 [thread overview]
Message-ID: <a1046060b96996bb5591ff18f47b8a0960e0c56e.camel@xry111.site> (raw)
Hi,
When I run Binutils 2.42 test suite with GCC 14 installed, several tests
failed:
FAIL: Handle no DWARF information
FAIL: undefined function
FAIL: undefined line
These seem just a mismatch in the error message due to the ".Lla-relax-
align" symbol and I'd consider them a minor issue.
FAIL: Check --gc-section
FAIL: Check --gc-section/-q
FAIL: Check --gc-section/-r/-e
FAIL: Check --gc-section/-r/-u
These seem a real issue, see
https://github.com/loongson-community/discussions/issues/40.
Could you please take a look at them? I'm sorry that testing Binutils
before 2.42 release with GCC 14 had never came into my mind :(.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next reply other threads:[~2024-02-01 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 20:38 Xi Ruoyao [this message]
2024-02-02 1:33 ` mengqinggang
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=a1046060b96996bb5591ff18f47b8a0960e0c56e.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=cailulu@loongson.cn \
--cc=mengqinggang@loongson.cn \
/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).