public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Wileam Yonatan Phan <wileamyp@outlook.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Clarification on newlib version for building AMDGCN offloading backend
Date: Tue, 7 Mar 2023 15:38:08 +0000	[thread overview]
Message-ID: <99e77e25-0c83-1087-691d-43530e7395b3@codesourcery.com> (raw)
In-Reply-To: <BY5PR14MB39111EC7D08E50D950A7126DCEB69@BY5PR14MB3911.namprd14.prod.outlook.com>

On 06/03/2023 19:23, Wileam Yonatan Phan via Gcc wrote:
> Hi,
> 
> I'm working on adding a build recipe for GCC with AMDGCN offloading backend in Spack. Can anyone clarify the following sentence listed on the wiki?
> 
>> The Newlib version needs to be contemporaeous with GCC, at least until the ABI is finalized.
> <https://gcc.gnu.org/wiki/Offloading#How_to_build_an_offloading-enabled_GCC>
> 
> What are the correct contemporaneous versions for each version of GCC >= 10?

Just match the dates and you'll probably be fine. We've mostly 
synchronised the ABI changes across the GCC mainline and the development 
branch precisely because the Newlib dependency is shared.

Right now the required version of Newlib is 4.3.0.20230120. Prior to the 
ABI change a month or so ago you would have to use a Newlib snapshot.

I wouldn't recommend spending very much of your valuable time on 
enabling old versions of these toolchains.

Andrew

  reply	other threads:[~2023-03-07 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 19:23 Wileam Yonatan Phan
2023-03-07 15:38 ` Andrew Stubbs [this message]
2023-03-07 18:42   ` Wileam Yonatan Phan
2023-03-29 18:18     ` Wileam Yonatan Phan
2023-03-30  8:45       ` Andrew Stubbs
2023-06-30 21:06         ` Wileam Yonatan Phan
2023-07-03  9:02           ` Stubbs, Andrew

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=99e77e25-0c83-1087-691d-43530e7395b3@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=wileamyp@outlook.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).