public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100208] amdgcn fails to build with llvm-mc from llvm12
Date: Mon, 18 Oct 2021 08:57:21 +0000	[thread overview]
Message-ID: <bug-100208-4-j3asRl3D5u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100208-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100208

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Tobias Burnus
<burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:9552afb2aec54b793d61ce85c93869a2f2a7958f

commit r11-9162-g9552afb2aec54b793d61ce85c93869a2f2a7958f
Author: Andrew Stubbs <ams@codesourcery.com>
Date:   Thu Jul 8 15:47:53 2021 +0100

    amdgcn: Add -mxnack and -msram-ecc [PR 100208]

    gcc/ChangeLog:

            PR target/100208
            * config/gcn/gcn-hsa.h (DRIVER_SELF_SPECS): New.
            (ASM_SPEC): Set -mattr for xnack and sram-ecc.
            * config/gcn/gcn-opts.h (enum sram_ecc_type): New.
            * config/gcn/gcn-valu.md: Add a warning comment.
            * config/gcn/gcn.c (gcn_option_override): Add "sorry" for -mxnack.
            (output_file_start): Add xnack and sram-ecc state to
".amdgcn_target".
            * config/gcn/gcn.md: Add a warning comment.
            * config/gcn/gcn.opt: Add -mxnack and -msram-ecc.
            * config/gcn/mkoffload.c (EF_AMDGPU_MACH_AMDGCN_GFX908): Remove
            SRAM-ECC flag.
            (EF_AMDGPU_XNACK): New.
            (EF_AMDGPU_SRAM_ECC): New.
            (elf_flags): New.
            (copy_early_debug_info): Use elf_flags.
            (main): Handle -mxnack and -msram-ecc options.
            * doc/invoke.texi: Document -mxnack and -msram-ecc.

    gcc/testsuite/ChangeLog:

            PR target/100208
            * gcc.target/gcn/sram-ecc-1.c: New test.
            * gcc.target/gcn/sram-ecc-2.c: New test.
            * gcc.target/gcn/sram-ecc-3.c: New test.
            * gcc.target/gcn/sram-ecc-4.c: New test.
            * gcc.target/gcn/sram-ecc-5.c: New test.
            * gcc.target/gcn/sram-ecc-6.c: New test.
            * gcc.target/gcn/sram-ecc-7.c: New test.
            * gcc.target/gcn/sram-ecc-8.c: New test.

    (cherry picked from commit aad32a00b7d2b64ae158b2b167768a9ae3e20f6e)

  parent reply	other threads:[~2021-10-18  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 12:37 [Bug target/100208] New: " rguenth at gcc dot gnu.org
2021-04-22 14:01 ` [Bug target/100208] " ams at gcc dot gnu.org
2021-07-19 16:37 ` cvs-commit at gcc dot gnu.org
2021-07-21  9:30 ` ams at gcc dot gnu.org
2021-07-28 13:04 ` cvs-commit at gcc dot gnu.org
2021-10-18  8:57 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-18  8:57 ` cvs-commit 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-100208-4-j3asRl3D5u@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).