public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [og12] Un-break nvptx libgomp build (was: [OG12][committed] amdgcn: OpenMP low-latency allocator)
Date: Mon, 20 Feb 2023 09:34:42 +0000	[thread overview]
Message-ID: <40311cae-13d5-e3a0-5500-5c35f82b306d@codesourcery.com> (raw)
In-Reply-To: <87zg9dxqlp.fsf@euler.schwinge.homeip.net>

On 16/02/2023 21:11, Thomas Schwinge wrote:
>> --- /dev/null
>> +++ b/libgomp/basic-allocator.c
> 
>> +#ifndef BASIC_ALLOC_YIELD
>> +#deine BASIC_ALLOC_YIELD
>> +#endif
> 
>      In file included from [...]/libgomp/config/nvptx/allocator.c:49:
>      [...]/libgomp/config/nvptx/../../basic-allocator.c:52:2: error: invalid preprocessing directive #deine; did you mean #define?
>         52 | #deine BASIC_ALLOC_YIELD
>            |  ^~~~~
>            |  define
> 
> Yes, indeed.
> 
> I've pushed to devel/omp/gcc-12 branch
> commit 6cc0e7bebf1b3ad6aacf75419e7f06942409f90c
> "Un-break nvptx libgomp build", see attached.

Oops, thanks Thomas.

Andrew

  reply	other threads:[~2023-02-20  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 18:06 [OG12][committed] amdgcn: OpenMP low-latency allocator Andrew Stubbs
2023-02-16 21:11 ` [og12] Un-break nvptx libgomp build (was: [OG12][committed] amdgcn: OpenMP low-latency allocator) Thomas Schwinge
2023-02-20  9:34   ` Andrew Stubbs [this message]
2023-03-24 16:30 ` [OG12][committed] amdgcn: OpenMP low-latency allocator Thomas Schwinge

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=40311cae-13d5-e3a0-5500-5c35f82b306d@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=thomas@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).