public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108981] New: Raise errors for cpu type without powerpc64 support. Date: Wed, 01 Mar 2023 05:35:02 +0000 [thread overview] Message-ID: <bug-108981-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108981 Bug ID: 108981 Summary: Raise errors for cpu type without powerpc64 support. Product: gcc Version: 13.0 URL: https://gcc.gnu.org/pipermail/gcc-patches/2023-January /609492.html Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: linkw at gcc dot gnu.org CC: bergner at gcc dot gnu.org, linkw at gcc dot gnu.org, marxin at gcc dot gnu.org, segher at gcc dot gnu.org Depends on: 108240 Blocks: 108415 Target Milestone: --- Target: powerpc +++ This bug was initially created as a clone of Bug #108240 +++ Currently for the explicitly given option -m64 and the cpu type without powerpc64 support like cpu 401, we just go with -m64 and powerpc64 enabled and there is no any warnings or errors. Without any explicit option -m64 or -m32 but it's set as 64bit env from TARGET_DEFAULT, for the cpu type without powerpc64 support like cpu 401, we will emit errors on Linux and warnings on aix and darwin. As Segher pointed out in PR108240, we've better to make them be handled consistently, that is to raise errors and prevent this non-sense usage, open this for further tracking. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108240 [Bug 108240] [13 Regression] Error message missing since r13-4894-gacc727cf02a144 (then make concealed ICE exposed) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108415 [Bug 108415] ICE in emit_library_call_value_1 at gcc/calls.cc:4181
next reply other threads:[~2023-03-01 5:35 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-01 5:35 linkw at gcc dot gnu.org [this message] 2023-03-01 5:36 ` [Bug target/108981] " linkw at gcc dot gnu.org
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-108981-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: 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).