public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113684] Cross compiler without assembler and linker should assume that all assembler and linker features are available Date: Thu, 01 Feb 2024 13:54:06 +0000 [thread overview] Message-ID: <bug-113684-4-U2Qtvh6rAF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113684-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113684 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I'm not sure it is a good idea to essentially say yes on all gas or linker tests without actually undestanding what those tests do. Because not all tests are supposed to pass on latest binutils, some are supposed to pass only on some targets and not on others, some could be checking for older bugs, etc. Now, I believe for linker tests we for the in tree case we have hardcoded what versions support certain features, so perhaps the no linker case could be handled similarly (and perhaps let the user even specific the ld date/version to be assumed). Assembler tests are done always even with in-tree builds though, so I think we'd need to amend them since which version something works, on which target etc.
next prev parent reply other threads:[~2024-02-01 13:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-31 16:11 [Bug target/113684] New: " hjl.tools at gmail dot com 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 [this message] 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-U2Qtvh6rAF@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: linkBe 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).