From: Jeff Law <jeffreyalaw@gmail.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 5/5] match.pd: Use splits in makefile and make configurable.
Date: Fri, 5 May 2023 09:13:47 -0600 [thread overview]
Message-ID: <5296e8d8-6b8a-99e3-eb98-bf8589c0903a@gmail.com> (raw)
In-Reply-To: <VI1PR08MB532580BE67A0ABEB86A538BAFF729@VI1PR08MB5325.eurprd08.prod.outlook.com>
On 5/5/23 09:08, Tamar Christina wrote:
>> -----Original Message-----
>> From: Jeff Law <jeffreyalaw@gmail.com>
>> Sent: Friday, May 5, 2023 4:04 PM
>> To: David Edelsohn <dje.gcc@gmail.com>; Tamar Christina
>> <Tamar.Christina@arm.com>
>> Cc: GCC Patches <gcc-patches@gcc.gnu.org>
>> Subject: Re: [PATCH 5/5] match.pd: Use splits in makefile and make
>> configurable.
>>
>>
>>
>> On 5/5/23 08:59, David Edelsohn via Gcc-patches wrote:
>>> This patch has broken GCC bootstrap on AIX. It appears to rely upon,
>>> or complain about, the command "seq":
>>>
>>> /nasfarm/edelsohn/install/GCC12/bin/g++ -std=c++11 -g -DIN_GCC
>>> -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
>>> -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-format
>>> -Wmissing-format-attribute -Wconditionally-supported
>>> -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
>>> -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -
>> DGENERATOR_FILE
>>> -static-libstdc++ -static-libgcc -Wl,-bbigtoc -Wl,-bmaxdata:0x40000000 -o
>> build/genmatch \
>>> build/genmatch.o ../build-powerpc-ibm-aix7.2.5.0/libcpp/libcpp.a
>>> build/errors.o build/vec.o build/hash-table.o build/sort.o
>>> ../build-powerpc-ibm-aix7.2.5.0/libiberty/libiberty.a
>>> /usr/bin/bash: seq: command not found
>>> /usr/bin/bash: seq: command not found
>>> build/genmatch --gimple \
>>> --header=tmp-gimple-match-auto.h --include=gimple-match-auto.h \
>>> /nasfarm/edelsohn/src/src/gcc/match.pd
>>>
>>> All of the match files are dumped to stdout.
>> Sigh. So the question is do we make seq a requirement or do we implement an
>> alternate to get the sequence or implement a fallback.
>>
>> jeff
>
> I'm looking for an alternate sequence now.
>
> If I don't find one in a bit, since Monday is a bank holiday for the UK I can temporarily
> Ignore the configure flag by defining
>
> MATCH_SPLITS_SEQ = 1 2 3 4 5 6 7 8 9 10
>
> Would that be ok as a temporary fix if I don't find anything else by EOD? But hoping to find another way that doesn't rely on coreutils.
Yea, that would be a fine workaround while we sort this out.
jeff
next prev parent reply other threads:[~2023-05-05 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 14:59 David Edelsohn
2023-05-05 15:04 ` Jeff Law
2023-05-05 15:08 ` Tamar Christina
2023-05-05 15:13 ` Jeff Law [this message]
2023-05-05 15:17 ` Jakub Jelinek
2023-05-05 15:22 ` Tamar Christina
2023-05-05 15:33 ` Jakub Jelinek
2023-05-05 15:37 ` Tamar Christina
2023-05-05 15:41 ` David Edelsohn
2023-05-05 20:46 ` Jakub Jelinek
2023-05-05 23:32 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 10:44 Tamar Christina
2023-04-30 19:46 ` Jeff Law
2023-05-02 7:08 ` Tamar Christina
2023-05-03 15:18 ` Kyrylo Tkachov
2023-05-04 9:56 ` Tamar Christina
2023-05-04 23:25 ` Jeff Law
2023-05-05 12:51 ` Tamar Christina
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=5296e8d8-6b8a-99e3-eb98-bf8589c0903a@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Tamar.Christina@arm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@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).