From: Joseph Myers <joseph@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: Kwok Cheung Yeung <kcy@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] openmp: Add support for the 'indirect' clause in C/C++
Date: Tue, 7 Nov 2023 21:37:22 +0000 [thread overview]
Message-ID: <67d99da-e69-56b4-1785-38b964143ec9@codesourcery.com> (raw)
In-Reply-To: <be6109ab-e43c-4ec3-b2f8-b8f760449431@codesourcery.com>
I'm seeing build failures "make[5]: *** No rule to make target
'target-indirect.c', needed by 'target-indirect.lo'. Stop." for many
targets in my glibc bot.
https://sourceware.org/pipermail/libc-testresults/2023q4/012061.html
FAIL: compilers-arc-linux-gnu gcc build
FAIL: compilers-arc-linux-gnuhf gcc build
FAIL: compilers-arceb-linux-gnu gcc build
FAIL: compilers-csky-linux-gnuabiv2 gcc build
FAIL: compilers-csky-linux-gnuabiv2-soft gcc build
FAIL: compilers-m68k-linux-gnu gcc build
FAIL: compilers-m68k-linux-gnu-coldfire gcc build
FAIL: compilers-m68k-linux-gnu-coldfire-soft gcc build
FAIL: compilers-microblaze-linux-gnu gcc build
FAIL: compilers-microblazeel-linux-gnu gcc build
FAIL: compilers-nios2-linux-gnu gcc build
FAIL: compilers-or1k-linux-gnu-soft gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imac-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d gcc build
FAIL: compilers-sh3-linux-gnu gcc build
FAIL: compilers-sh3eb-linux-gnu gcc build
FAIL: compilers-sh4-linux-gnu gcc build
FAIL: compilers-sh4-linux-gnu-soft gcc build
FAIL: compilers-sh4eb-linux-gnu gcc build
FAIL: compilers-sh4eb-linux-gnu-soft gcc build
FAIL: compilers-x86_64-gnu gcc build
This looks like targets that libgomp/configure.tgt does *not* have any
special handling for, and so never adds "linux" to config_path for.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-11-07 21:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 13:13 Kwok Cheung Yeung
2023-10-17 13:12 ` Tobias Burnus
2023-10-17 13:34 ` Jakub Jelinek
2023-10-17 14:41 ` Tobias Burnus
2023-11-03 19:53 ` Kwok Cheung Yeung
2023-11-06 8:48 ` Tobias Burnus
2023-11-07 21:37 ` Joseph Myers [this message]
2023-11-07 21:51 ` Jakub Jelinek
2023-11-07 21:59 ` Kwok Cheung Yeung
2023-11-09 12:24 ` Thomas Schwinge
2023-11-09 16:00 ` Tobias Burnus
2023-11-13 10:59 ` Thomas Schwinge
2023-11-13 11:47 ` Tobias Burnus
2024-04-11 10:10 ` Thomas Schwinge
2024-01-03 14:47 ` [committed] " Kwok Cheung Yeung
2024-01-03 15:54 ` Kwok Cheung Yeung
2024-01-22 20:33 ` [PATCH] openmp: Change to using a hashtab to lookup offload target addresses for indirect function calls Kwok Cheung Yeung
2024-01-24 7:06 ` rep.dot.nop
2024-01-29 17:48 ` [PATCH v2] " Kwok Cheung Yeung
2024-03-08 13:40 ` Thomas Schwinge
2024-03-14 11:38 ` Tobias Burnus
2024-01-22 20:41 ` [PATCH] openmp, fortran: Add Fortran support for indirect clause on the declare target directive Kwok Cheung Yeung
2024-01-23 19:14 ` Tobias Burnus
2024-02-05 21:37 ` [PATCH v2] " Kwok Cheung Yeung
2024-02-06 9:03 ` Tobias Burnus
2024-02-06 9:50 ` Kwok Cheung Yeung
2024-02-12 8:51 ` Tobias Burnus
2024-02-15 21:37 ` [COMMITTED] libgomp: Update documentation for indirect calls in target regions Kwok Cheung Yeung
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=67d99da-e69-56b4-1785-38b964143ec9@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kcy@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).