public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	Julian Brown <julian@codesourcery.com>
Cc: Matthias Klose <doko@ubuntu.com>
Subject: Re: [Patch][GCN] [GCC 11] Backport GCN with LLVM-MC 13 linker fixes to GCC 11
Date: Mon, 18 Oct 2021 09:54:59 +0100	[thread overview]
Message-ID: <56f8a8f7-4349-0f96-144a-0f9e13b2c43b@codesourcery.com> (raw)
In-Reply-To: <48979236-ccd7-37a8-9900-d699eb834ff4@codesourcery.com>

This is fine by me.

As I said in my email on the 15th, LLVM 13 is still not considered safe 
to use. The ICE you encountered is a real problem that will affect real 
users.

I expect to work on a solution for that soon.

Andrew

On 16/10/2021 21:41, Tobias Burnus wrote:
> This patch is mostly motivated by distribution needs in general
> and Debian/Ubuntu needs in particular – but I think it makes
> sense for all GCC 11 users.
> 
> GCC's AMD GCN support uses LLVM's assembler and linker mc/lld
> and thus requires compatibility with LLVM. On mainline, support
> for LLVM 13 was added – and I like to see a backport to GCC 11.
> 
> In particular, I would like to "git cherry-pick -x' the following patches:
> 
> cfa1f8226f2 gcc/configure.ac: fix register issue for global_load 
> assembler functions
> aad32a00b7d amdgcn: Add -mxnack and -msram-ecc [PR 100208]
> 5c127c4cac3 amdgcn: Mark s_mulk_i32 as clobbering SCC
>   (Outside of this series as it only picks a bug fix)
> 6ca03ca35a5 amdgcn: Support LLVM 13 assembler syntax
>   (-> see remark below)
> 205dafb6ede amdgcn: Implement -msram-ecc=any
> 81c362c7c2b amdgcn: Fix assembler version incompatibility
> f3d64372d77 amdgcn: fix up offload debug linking with LLVM 13
> 
> OK for GCC 11?
> 
> [I have build GCC x86-64 with amdgcn offloading enabled both
> with LLVM 9 and with LLVM 13; libgomp passes fine with LLVM 9
> but with the LLVM 13 build, I see an ICE in lld for some testcases,
> which I have not debugged – but GCC itself builds and several
> libgomp testcases do pass.]
> 
> Tobias
> 
> PS: I attached
> * the full "git log --stat" for all those patches for references
> * as the 4th one, "Support LLVM 13 assembler syntax", does not
>    cleanly apply, I attached the full patch.
> 
> The reason that the latter does not apply is that mainline changed:
> "configure: remove version argument from gcc_GAS_CHECK_FEATURE"
> in https://gcc.gnu.org/g:e0b6d0b39c69372e4a66f44d218e0244bb549d83
> which was fixed for GCN a bit later in commit
> "configure: Adjust several assembler checks to remove an unused parm."
> https://gcc.gnu.org/g:e5d9873fcb6f90d03b7534af53de39ec65d0cdc5
> 
> The only change is "," to ",," in configure.ac; 'configure' itself
> was already fine.
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 
> 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: 
> Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; 
> Registergericht München, HRB 106955


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 20:41 Tobias Burnus
2021-10-18  8:54 ` Andrew Stubbs [this message]

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=56f8a8f7-4349-0f96-144a-0f9e13b2c43b@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=julian@codesourcery.com \
    --cc=tobias@codesourcery.com \
    /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).