public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113684] New: Cross compiler without assembler and linker should assume that all assembler and linker features are available
Date: Wed, 31 Jan 2024 16:11:42 +0000 [thread overview]
Message-ID: <bug-113684-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113684
Bug ID: 113684
Summary: Cross compiler without assembler and linker should
assume that all assembler and linker features are
available
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
When configuring GCC with
--target=TARGET
to build a cross compiler to reproduce a compiler bug, as and collect have
ORIGINAL_AS_FOR_TARGET=""
ORIGINAL_LD_FOR_TARGET=""
As the result, many target features are disabled which makes it almost
impossible
to reproduce the bug. When there are no as nor ld, the compiler build isn't
a working build. In this case, configure can assume that all assembler and
linker features are available so that the partially built cross compiler can
be used to reproduce the bug.
next reply other threads:[~2024-01-31 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 16:11 hjl.tools at gmail dot com [this message]
2024-01-31 17:49 ` [Bug target/113684] " pinskia at gcc dot gnu.org
2024-01-31 17:51 ` pinskia at gcc dot gnu.org
2024-01-31 18:01 ` hjl.tools at gmail dot com
2024-02-01 7:32 ` rguenth at gcc dot gnu.org
2024-02-01 13:43 ` hjl.tools at gmail dot com
2024-02-01 13:54 ` jakub at gcc dot gnu.org
2024-02-01 16:45 ` hjl.tools at gmail dot com
2024-02-01 16:48 ` jakub at gcc dot gnu.org
2024-02-01 17:00 ` hjl.tools at gmail dot com
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=bug-113684-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).